2,737 research outputs found
The Technological Education Institutes (TEI) in Greece and their libraries
No full textThe legal framework for the foundation of the Technological
Education Institutes (TEI) in Greece is presented. A short history of the education of the librarians in Greece and some general information about all the Institutes and their libraries is given. Data for the organisation, automation and personnel of the libraries are presented
simondschweitzer/aed-tei: AED-TEI Version 1.0
No full textPublication of more than 11000 Egyptian texts in the TEI format, and ...
TEI schema
dictionary
thesaurus
morphological features
Project: AED - Ancient Egyptian Dictionary https://simondschweitzer.github.io/aed/
License: CC-BY-SA-4.0
Source: https://nbn-resolving.org/urn:nbn:de:kobv:b4-opus4-2919
Dialogue and linking between TEI and other semantic models
No full textThe deep dialogue TEI started with other semantic models – i.e. CIDOCCRM and FRBR/FRBR (OO) has two aims: the data and documents interchange and the improvement of the editors possibilities to formally declare hermeneutical positions. The TEI schema provides most of the elements/attributes (and classes) useful to describe interpretation instances, while further schemas, as well as other value vocabularies and metadata element sets, are supposed to enhance some potentialities of the model itself. On one hand, additional schemas could contribute to perfect the scope of some TEI elements, while on the other, the existing ontologies could improve the interpretation effectiveness.
Therefore, this panel is aimed at introducing three different approaches to document representation, where TEI may draw some hints from other models.
We first present the contribute of EAC (Encoded Archival Context) to extend people’s description, starting from the archival approach to the context, here intended as the key element to define individual’s roles and functions.
Then we considered the dialogue between TEI and the existing
ontologies, with particular attention to geographic data.
Finally, thanks to the ‘semantic lenses’ employed as an exploratory tool for annotated documents, we started up the relationship between TEI and specific ontologies related to semantic publishing
TEI P5: Guidelines for Electronic Text Encoding and Interchange
No full textFind more information about the Text Encoding Initative at https://tei-c.orgTEI P5 version 3.3.0 release notesRelease 3.3.0 (code name: Johnny Rotten) of the TEI Guidelines introduces new features and resolves a number of issues raised
by the TEI community. As always, the majority of these changes and corrections are
a consequence of feature requests or bugs reported by the TEI community using the
GitHub tracking system. A full list of the issues resolved in the course of this release
cycle may be found under the 3.3.0 milestone.
Highlights of this release include:
A new attribute class att.linguistic has been introduced. The existing attributes lemma and lemmaRef are now members of the new attribute class, the attributes pos, msd and join were newly introduced. The elements w and pc are members of att.linguistic (#1670).
The form element is now a member of att.typed (#1688).
The gb element is now a member of att.edition (#1677).
The element etym is now a member of att.typed and permits recursive etym elements (#1512).
The elements c, cl, hyph, m, orth, phr, quote, s, seg, stress, syll and w are now members of att.notated, and thus now can have the notation attribute (#1510, #1514, #1734).
remarks is now permitted as a child of valItem if desc is also a child (#1420).
bibl is now permitted in witDetail (#1425).
The content model of affiliation in the jTEI schema has been expanded and allows placeName now (#1692).
A number of content models have been improved, including:
the listRef element (#1674)
the content element (#1719, #1716)
the choice element (#1690)
The explanations and discussions of several features have been improved:
the inconsistent definition of the reason attribute for gap and unclear has been unified (#1729)
the description of the content element has been clarified (#1718), as well as the prose discussing its use for writing content models (#1459)
the description of the move element has been clarified (#1705)
A new Exemplar called tei_customization has been added. It supports writing a TEI
customization by hand (#1349).
The appendices A to E now mention the number of distinct items included in them (#1517).
The macro macro.anyXML is now deprecated (#1585), as anyElement is available.
Dozens of wording improvements and corrections of typographic errors have been made
to the Guidelines.
In addition, many improvements have been made to the XSLT stylesheets (which provide
processing of TEI ODD files for Roma and OxGarage as well as other TEI conversions). The Stylesheets are maintained separately from
the Guidelines and are at https://github.com/TEIC/Stylesheets.
Home Feedback
Date: 2018-01-31released under the
Creative Commons Attribution 3.0 Unported License
http://creativecommons.org/licenses/by/3.0
I remember working at Seabrook
No full textIn this "I remember" memoir, Tei Sasho recalls how he was invited to Seabrook to assist Dick Kunishima with establishing and running a grocery store, a cafeteria, and a baseball team. Mr. Sasho worked at Seabrook for three years, where he also met and married his wife. The Seabrook Educational and Cultural Center has been soliciting current and past residents of Seabrook Farms for an "I remember" project. Residents are asked to create narratives regarding their experiences at Seabrook Farms. These memories help preserve the history and multi-cultural heritage of Seabrook Farms
Islandora and TEI
No full textIslandora is an open-source software framework developed since 2006 by the University of Prince Edward Island's Robertson Library. The Islandora framework is designed to ease the management of security and workflow for digital assets, and to help implementers create custom interfaces for display, search, and discovery. Turnkey options are provided via tools and modules ("solution packs") designed to support the work of a particular knowledge domain (such as chemistry), a particular content type (such as a digitized newspaper), or a particular task (such as TEI encoding). While it does not yet have native support for TEI, Islandora provides a promising basis on which digital humanities scholars could manage the creation, editing, validation, display, and comparison of TEI-encoded text. UPEI's IslandLives project, with its forthcoming solution pack, provides insight into how an Islandora version 6 installation can support OCR text extraction, automatic structural/semantic encoding of text, and web-based TEI editing and display functions for site administrators. This article introduces the Islandora framework and its suitability for TEI, describes the IslandLives approach in detail, and briefly discusses recent work and future directions for TEI work in Islandora. The authors hope that interested readers may help contribute to the expansion of TEI-related services and features available to be used with Islandora
Digitale Editionsformen. Zum Umgang mit der Überlieferung unter den Bedingungen des Medienwandels. Teil 3: Textbegriffe und Recodierung. [Preprint-Fassung]
No full textDie wissenschaftliche Edition zielt auf die zuverlässige Wiedergabe des Textes. Aber was ist dieser Text eigentlich? Bei genauerer Betrachtung erlaubt nur ein erweiterter Textbegriff und ein neues pluralistisches Textmodell eine Beschreibung aller textuellen Phänomene, die in einer wissenschaftlichen Edition zu berücksichtigen sind. Auch unsere Technologien und Methodologien der Textcodierung, hier vor allem die Auszeichnungssprachen im Allgemeinen und die Beschreibungsempfehlungen der Text Encoding Initiative (TEI) im Besonderen können unter dieser Schablone genauer beschrieben und hinsichtlich ihrer Grenzen charakterisiert werden. Schließlich erlaubt das pluralistische Textmodell auch die präzisere theoretische Fundierung jener Prozesse, die als "Transkription" Grundlage und Herzstück einer jeden wissenschaftlichen Edition sind
TEI P5: Guidelines for Electronic Text Encoding and Interchange
No full textFind more information about the Text Encoding Initative at https://tei-c.orgP5 version 1.3 release notesThis release:
adds two new elements (listEvent and locusGrp)
includes extensive modifications to the French translation, undertaken by the GE8
group under J-L. Benoit
includes a large number of Chinese examples provided by the Taiwan team under M. Bingenheimer
contains a range of minor changes agreed by the TEI Council between November 2008
and January 2009, in response to suggestions and bug reports received at the TEI Sourceforge
request tracker.
Changes made are listed briefly below in date order. Where further discussion of the
change is available in the SF bug tracker, the ticket number is indicated in parentheses
below:
2008-11-01: Permit milestone elements within the body of listBibl (2510548)
2008-11-01: Add Korean translations for most element specifications
2008-11-17: Change text of HD and MS to clarify recommendations about where lb etc. should be placed
2008-12-08: Simplify definition for Tei "Bare" exemplar
2008-12-09: Clarify descriptions for elements desc and sourceDesc (2055880)
2008-12-12: Add origPlace to add.datable class, for consistency with origDate (2100015)
2008-12-12: Permit titlePage as an explicit alternative within msContents (2242183)
2009-01-05: Add new French translated material
2009-01-10: Add new Chinese translated material
2009-01-12: Correct erroneous examples in specifications for supplied, population, listPerson
2009-01-12: Permit multiple instances of valDesc to support different language versions
2009-01-15: Add columns to list of suggested values for biblScope (2510582)
2009-01-16: Remove redundant usage attributes from all element specs and from elementSpec (2411987); at the same time removed all currently redundant xml:id values on element specs
2009-01-16: Resolve some unresolved pointers in examples introduced by Chinese translations
2009-01-19: Add new class att.sourced to supply ed attribute (2216574)
2009-01-22: Simplify list of suggested values for place attribute (2507349)
2009-01-23: Add new element listEvent (2056408)
2009-01-23: Add brief note deprecating use of targetEnd (2494567)
2009-01-23: Add term to att.canonical class and revise discussion in CO (2201246)
2009-01-24: Link Chinese examples with Chinese source information
2009-01-24: Correct some erroneous bibliographic links for examples
2009-01-24: Permit empty valList and null prefix on schemaSpec
2009-01-27: Correct typo (declarable for declaring) in CC
2009-01-27: Add ab lg and p to class att.declaring (2538659)
2009-01-30: Add new element locusGrp and revise discussion in MS extensively (2242024)
Home Feedback
Date: 2009-02-01released under the
Creative Commons Attribution 3.0 Unported License
http://creativecommons.org/licenses/by/3.0
Text markup using the TEI and collations using the MVED: a comparison of text encoding schemes in producing electronic text
No full textDue to the character of the original source materials and the nature of batch digitization, quality control issues may be present in this document. Please report any quality issues you encounter to [email protected], referencing the URI of the item.Includes bibliographical references (leaves 35-38).Issued also on microfiche from Lange Micrographics.The Cervantes Project aims to create an EVE (Electronic Variorum Edition) from existing copies of the Don Quixote de la Mancha novel by the Spanish author Cervantes. This process involves collating text versions of the many available copies of the book. During the collation process, the editor, a Spanish scholar, corrects, emends, and annotates portions of the texts. The tool within the Cervantes Project that helps in doing this is the Multi-Variant Editor for Documents (MVED). The aim is to develop a set of interlinked texts and images, having all the corrections, emendations, and annotations in place. This set is the EVE. Thus, the text files are manipulated in multiple ways within the collation process. The manipulations are stored in a database repository, without modifying the actual texts themselves. In a sense, we are encoding the text document that we are working with. The TEI (Text Encoding Initiative) standard was launched in 1987 to electronically encode all kinds of text documents, using a scheme that is simple yet powerful. The TEI DTD defines tags that can reflect how text documents are encoded, and how they are modified. This thesis aims to find a parallel between the encoding schemes provided by the MVED and the TEI. It aims to compare the two initiatives in encoding text documents, and find out the strengths and weaknesses of each. The MVED was developed much after the TEI was founded, and uses recent advances in computer technology to assist the end user in encoding the text document. We aim to compare the two processes, i.e., the processes of encoding using the MVED and the TEI, to find similarities between the two. We hope to be able to encode part of the EVE in the TEI specified format, with all the information encoded by the MVED. Also, we hope to study the advantages or disadvantages of data abstraction as provided by the MVED. As a part of the comparison process, we provide functionality within the MVED to encode the ongoing collation process using the TEI. In developing this tool (the Text2TEI Converter), we hope to cover all of the action points in comparing between the TEI and the MVED, as regard text encoding. This would involve converting the base text of the collation, with editorial modifications, into the TEI format
Chemical weed control in processing spinach
No full textProcessing spinach shows a good competitive ability and as a consequence yield losses due to weed competition are commonly low. Physical weed control gives reliable results (Tei et al., 2002) but weed management is still mainly chemical because: 1) the mechanical harvest needs a crop with an erect leaf posture favoured by a narrow row width (0.10 – 0.15 m) and that prevents the use of most post-emergence physical weed control methods; 2) processing industries demand harvested product without weeds, considered as “pollutant bodies” in industrial process. However, there are few herbicides registered for this crop.
For the above mentioned reasons, chemical weed control field experiments on processing spinach were carried out in southern (Foggia, silty-clay soil, mid-October 2001 sowing) and central Italy (Latina, silty-sandy soil, mid-March 2002 sowing) to verify the efficacy and selectivity of authorised herbicides (i.e. lenacil, cycloate) and to evaluate the performance of potential “new” active ingredients (phenmedipham, metamitron, desmedipham) already used in sugar beets. Several different combinations of active ingredients and application timing were evaluated: pre-emergence treatments with lenacil or metolachlor; post-emergence treatments (at 2-4 crop leaf stage) with phenmedipham + lenacil, phenmedipham + desmedipham, phenmedipham + cycloate or phenmedipham + metamitron; pre-emergence application of lenacil or metolachlor followed by post-emergence application of phenmedipham + metamitron, phenmedipham + cycloate, phenmedipham + desmedipham or phenmedipham + quizalofop-ethyl.
The most important weeds were Lolium multiflorum, Fumaria officinalis, Sinapis arvensis, Matricaria chamomilla, Veronica hederifolia in the southern Italy experiment and Chenopodium album, Stellaria media, Capsella bursa-pastoris, Amaranthus retroflexus and V. hederifolia in the central Italy experiment.
Among pre-emergence treatments, metolachlor did not significantly affect the crop while lenacil caused a temporary leaf discoloration. Metamitron and the combination phenmedipham + metamitron applied post-emergence caused a reduction in growth, leaf bleaching and necroses. The other post-emergence treatments showed slight symptoms of phytotoxicity just after the application that disappeared one week later.
Pre-emergence metolachlor controlled L. multiflorum, F. officinalis and V. hederifolia, but showed a low control of S. arvensis; lenacil sufficiently controlled only F. officinalis. Considering the efficacy of post-emergence applications, phenmedipham + lenacil and phenmedipham + metamitron exhibited good control of F. officinalis, but they were only partially effective toward L. multiflorum, S. arvensis, and C. album, and completely ineffective against V. hederifolia. Phenmedipham + desmedipham partially controlled all the weeds, while phenmedipham + cycloate showed a general good efficacy except on L. multiflorum.
The results indicated that a pre-emergence herbicide application with metolachlor followed by a post-emergence treatment with phenmedipham + cycloate or phenmedipham + lenacil was the most suitable chemical weed management.
However, spinach yield was not significantly affected by weed competition and herbicide efficacy but only by phytotoxicity due to post-emergence phemnmedipham + metamitron. Moreover, the presence of weeds, as “pollutant bodies” in harvested product, was always at very low level due to the possibility to regulate the harvest height in relation to crop and weed growth.
Reference
Tei F., Stagnari F. & Granier A. (2002) Preliminary results on physical weed control in processing spinach. 5th EWRS Workshop on Physical Weed Control. Pisa, Italy, 11-13 March 2002, 164-171 (http://www. EWRS-et.org/pwc/pdf/Pisa.pdf)
- …
