1 / 12

CRMepi and CRMtex Updates

Explore the transition from CRMepi to CRMtex, focusing on refining text segmentation, TEI and EpiDoc syntax, editorial interventions, and their mapping to CIDOC-CRM. Learn about tools like 3M Mapping, ARIADNE Summer School, and iSicily epigraphic archive. Discover future plans for CRMarchaeo and CRMtex standards. For more details, contact Achille Felicetti at achille.felicetti@pin.unifi.it.

bryanallen
Download Presentation

CRMepi and CRMtex Updates

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CRMepi and CRMtex Updates Achille Felicetti Francesca Murano Università degli Studi di Firenze, Italy

  2. CRMepi old classes EPI1 Epigraph “Subclass of E25 Man-Made Feature intended to describe a particular feature created by humans in various ways and on various kinds of support with the declared purpose of conveying a specific message towards a given recipient or group of recipients”

  3. From CRMepi to CRMtex: generalising concepts TX1 Written Text “Subclass of E25 Man-Made Feature intended to describe a particular feature (i.e., ‘set of glyphs’) created (i.e., written) on various kinds of support, having semiotic significance and the declared purpose of conveying a specific message towards a given recipient or group of recipients” EPI1 Epigraph “Subclass of E25 Man-Made Feature intended to describe a particular feature created by humans in various ways and on various kinds of support with the declared purpose of conveying a specific message towards a given recipient or group of recipients”

  4. CRMtex: from particular to general TX1 Written Text • “Subclass of E25 Man-Made Feature intended to describe a particular feature …” • “Epigraph”, “Engraving”: specific types of TX1 and TX2

  5. Text parts: identity and type definition • Going in depth: investigating interrelationships between text and text parts • Segmentation of ancient texts performed according with various typological/functional criteria • Fragments, columns, sections, chapters, lines, words … • Specific criteria for each discipline • Subdivision of text according with investigations carried out on it • Specific meaning for epigraphers, papyrologists, paleographists … • No objective general criteria for text subdivision in ancient texts documentation

  6. Text structure and EpiDoc • TEI and EpiDoc syntax inextricably related • Text subdivision and text parts • TEI <div> with a type="textpart” attribute + a subtype attribute naming the kind of subdivision ( "fragment", "column", "section”) • Words, characters, spaces, punctuation • TEI <w> element for specific words in the text • TEI <g> (for gliph) element for non-standard or non-alphabetic characters or glyphs • TEI <g type="interpunct"/> <g type="dipunct"/> • Text conditions, gaps • Damaged, erased, illegible or missing text parts • TEI <gap unit=“character”> <space unit=“character”>

  7. TEI, EpiDoc and editorial interventions • Editorial restoration of textual elements not present as features • TEI <supplied> element with specific EpiDoc customizations • Abbreviations fully expanded: • TEI <abbr> and <expan> elements with specific EpiDoc customizations • Corrections of erroneous characters • Superfluous characters to be eliminated • Editorial notes added to text description • Relationships between physical feature conditions and editorial renderings to be investigated

  8. CIDOC CRM and EpiDoc • EAGLE Project: EpiDoc mapping to CIDOC CRM • General conceptual mapping (CRM Information Carrier + Inscription) • No subclasses and subproperties definition for text and text structure • No general and predefined set of EpiDoc tags for text description • Different EpiDoc schema (i.e. XSD + XSL) for each discipline • Impossible to have a unique mapping for the whole TEI/ EpiDoc world • Different ad hoc mappings for each text class or school (or scholar!) • Specific mappings for each EpiDoc encoded archive

  9. CRMtex and text segments • To approximate text parts description

  10. CRMtex and EpiDoc • ARIADNE Summer School in July 2016 • iSicily: epigraphic archive of Sicilian inscriptions (EpiDoc) • 3M Mapping Tool + RDFS encoding of CRMtex used • EpiDoc to RDF transformation (partially) performed • CRMtex new classes • Verify coverage for related TEI/EpiDoc tags • RDF encoding of free texts transcriptions • XLink/XPointer to access the text portion

  11. Future Work • CRMarchaeo: preparation of scope notes for the new classes and properties • To complete the definition of superproperties for all CRMarchaeo properties • CRMtex: scope notes definition for the new classes and properties • CRMtex: preparation of a draft description document for the new extension to be submitted to SIG • CRMtex as candidate standard for the study of ancient texts

  12. Thank you • Achille Felicetti • PIN, Università degli Studi di Firenze, Italy • achille.felicetti@pin.unifi.it

More Related