| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

GuidelinesReorganizationDec2006

Page history last edited by PBworks 17 years, 3 months ago

Guidelines refactoring

 

Things to do in light of work Dec 2006 in RDU

 

Started, but did not finish, reorganizing the hierarchical structure of the guidelines. The goal is to break out of the constraints of following our individual typed to present things conceptually for an epigraphist audience. The business of "where does this tag belong?" is then subordinate to the larger conceptual tasks.

 

This reorganization was stimulated by a vigorous examination (still ongoing) of the descriptive categories and associated terminology used by the EDR project (see further: ControlledVocabularies). Concurrent work on the Crosswalker tool (specifically, its ability to import/export EDR data) was dependent upon (and advanced) this work.

 

Started but not finished

Specifically, we've:

  • Renamed "Tagging the Text" (taggingtext.xml) as "Transcribing and Editing the Text"
    • In this case, the guidelines section will continue to treat only things that can appear in the
      and, probably,
  • Created 3 new, first level guidelines sections as siblings of "Transcribing and Editing the Text":
    • "Describing the Text, the Support and the Context" (describing.xml)
    • "Interpretation: Analysis and Translation" (interpretation.xml)
    • "Recording and reporting" (recording.xml)
  • Saved a copy of "dates.xml" to "encodingdates.xml" and changed the include reference to it (which is still in the "Other Markup" section)
  • Saved a copy of "namesandpersons.xml" as "taggingnamesandpersons.xml" since this is technical, TEI encoding guidance

 

The above xml files (with their ids, etc.) now exist; however, various subordinate sections have been added to them as xi:includes, but the files to be included thereby do not yet exist (in other words, the guidelines are now broken).

 

So:

 

Yet to be done

 

Move the "Document Structure" section

 

Move this section (documentstructure.xml) to a later portion of the guidelines, and maybe make it suboridinate to a larger rubric like "technical encoding guidance", where also some things now lurking in "Other Markup Issues" would also go because they provide specific TEI encoding guidance that is needed in various contexts.

 

Lay out the next level of sections

 

Do this under the broad rubrics outlined above (transcribing, describing, transciption and recording) and create/move/reorganize guidelines source files to support the full hierarchy.

 

Specific tasks include:

  • Create stubs for the missing subsections that currently will break the webapp because there are xincludes for them that will fail to resolve to files
  • Check comments in the newly created stub files for additional things that should be added
  • Gut and rewrite as necessary all the various sections modified or introduced by this process
  • Look again at EDR categories and the corresponding epidoc encodings now produced by the crosswalker tool
    • ensure that all of these are treated conceptually (i.e., without close ties to EDR specifically)
    • incorporate the EDR/crosswalk specifics into our discussion of conformance

 

 

Fodder for intro to "Transcription and etc."

 

No time to do anthing useful with this now:

 

The fundamental act of an epigraphic publication is the presentation of the text.

 

EpiDoc offers the opportunity to tag at varying levels/depths. The minimal presentation may simply tag the text and being the text. The second level is to tag individual words in order to create a word index. A further, interpretative level is tagging principally of proper names (dates, titles, placenames and the like) to produce subject indices and faciliate searching. See further:

Comments (0)

You don't have permission to comment on this page.