Dear members of the TEI community,The Text Encoding Initiative Consortium (TEI-C) invites nominations for election to the TEI-C Board (4 positions available) and Technical Council (5 positions available). Following the recent revision of the bylaws, 5 positions are vacant on the Council and 4 positions are available on the TEI-C Board. Nominations for these should be sent to the nomination committee at nominations@tei-c.org by August 30, 2014. The elections will take place via electronic voting prior to the annual Members’ Meeting in October 2014.
Author: theteiadmin
3 Open DH Positions in Berlin
Dear Colleagues,
The Berlin-Brandenburg Academy of Sciences and Humanities (BBAW) is looking for three Digital Humanities specialists.
Further information (in German) can be found in the detailed job descriptions:
TELOTA (The electronic life of the academy) – full time, fixed-term until 31/12/2015
http://www.bbaw.de/stellenangebote/ausschreibungen-2014/2014-06-30_Ausschreibung_TELOTA_wiMi.pdf
Person data repository – part time, fixed-term for one year
http://www.bbaw.de/stellenangebote/ausschreibungen-2014/2014-06-30_Ausschreibung_PDR_wiMi.pdf
Music Migrations in the Early Modern Age – part time, fixed-term until 31/08/2016
http://www.bbaw.de/stellenangebote/ausschreibungen-2014/2014-06-30_Ausschreibung_MusMig-AV-10-2014_2.pdf
Best regards,
Alexander Czmiel
TEI Members Meeting, 2015 : call for bids
Dear Community,
Arrangements for this year’s annual TEI Members’ Meeting, to be hosted by Northwestern University, in Evanston Illinois, October 22–24, 2014 are now well in hand. (see http://tei.northwestern.edu/ for details). The TEI Board is now therefore starting the planning process for next year’s meeting, to be held some time in the autumn/fall of 2015.
Continue reading “TEI Members Meeting, 2015 : call for bids”
TEI Hackathon: Report by Elli Bleeker
Name: Elli Bleeker
Twitter: @ellibleeker
Email: elli.bleeker@uantwerpen.be
Working group project: ODD visualization
Contribution to group project: in comparison with the other participants, my experience with and knowledge of ODD and JSON was limited. Since it is very useful for anyone working with TEI XML to have at least a basic understanding of these concepts, I was happy to join this working group. At first, my contribution was mainly asking -perhaps obvious- questions about ODD. I’d like to think however that these questions helped to narrow down our goal. At least it was necessary to clearly describe the present state-of-the-art, what is missing, and why an ODD visualizer would be a welcome addition. During the workshop, I assisted with the creation of test data (several project-specific ODD, their transformation to flat ODD and subsequently to JSON); contributed on the design of the treemap and participated in the group discussions.
Methodology
The general idea and necessity of an ODD visualization was quickly explained, so the group focused on what exactly needs to be visualized and especially, how. The current ODD visualizer of Byzantium does not show the amount of customization. Moreover, it is useful to see on which specific areas the ODD focuses. We were quick in dividing into three smaller groups, each with specific assigned roles depending on our pre-existing knowledge and capabilities.
We decided upon a D3 zoomable treemap for the visualization of the amount of customization. The treemap shows how elements are grouped as well as –by their size or color- to what extent the elements are customized. The zoomable option could also allow to ‘zoom in’ on the customized elements to see the exact changes made.
Final Product
For all the deliverables (Google doc, Github, demo…), see the reports of the other group members.
Learning Outcomes
It was a very useful experience for me to work on this project. Although from time to time intimidating, the immediate jump from theory to practice was the best way to learn the concept (ODD, flat ODD, TEI schema, JSON, etc…) and to understand the workflow of the different processes. Having to think about the visualization of something that I was not familiar with helped me a great deal in understanding it. Whether the resulting visualization is as clear and useful for others remains to be tested. Nevertheless it is clear that this could be a necessary tool for users of TEI, regardless of their level of experience.
TEI Hackathon: Report by Elena Spadini
Name: Elena Spadini,
Twitter: @spadinelena
Email: elena.spadini@huygens.knaw.nl
Project: ODD visualization
Contribution: Discussion of the different steps with all the others.
Transformation from .odd to flat odd and then to .json
Contribution to the final design.
Documentation:
All links are available at https://docs.google.com/document/d/1u77xtS1WncnkjCwR9CpTfOYeW65q7meaXz7PM-Y5Tno/edit#heading=h.6w2vysqik2f4
Conclusions:
Final Product
http://tei.it.ox.ac.uk/Hackathon/odd/visualizer/index.html
Findings
We first discussed if and why it is interesting to have an ODD visualization. It can be useful both during the transcription stage, during which probably the schema continues to evolve; at the end of the process, to check immediatly and intuitive which are the mark-up “zones” where the customization was mainly working; to compare easily different customizations.
We found that the xslt from .odd to .json doesn’t take into account all datas: for instance, if a list of values for an attribute is closed or not and which are the mandatory ones or the suggested ones.
Learning outcomes
Discover the existence of some resources, as the d3 gallery (https://github.com/mbostock/d3/wiki/Gallery) or the tapasproject.org
Use for the first time new resources, as the different xslt stylesheets for TEI.
Most of all: enjoyng the discussion with scholars with different professional skills and approaches.
TEI Hackathon: Report by Raffaele Viglianti
Name: Raffaele Viglianti
twitter: @raffazizzi
github: https://github.com/raffazizzi
The project
We wanted to visualize some aspects of a given ODD specification to aid the creation process, or to help the understanding of someone else’s ODD.
There are some precedent attempts at doing this: Byzantium (http://tei.it.ox.ac.uk/Byzantium/) already visualizes basic information about what your ODD includes or excludes; Gregor Middell’s visualization (http://gregor.middell.net/roma/) already shows relationships between classes and elements in TEI.
We attempted to quantify *how much* an ODD has been customized and show graphically which parts have been curated more and which less.
My contribution
I worked on the architecture of this small app and programmed a scoring system that we previously sketched as a group.
First, the app imports a JSON version of the full TEI P5 ODD; then it imports the compiled ODD of a customization (in JSON).
Second, the ODDs are compared and scoring is calculated for each TEI element. These are the changes affecting the score (in parenthesis there are changes discussed, but not implemented):
* changed element description
* added attribute
* added attribute *value* (e.g. by restricting values for @type) <— this is by far the most common change
* (added elements)
* (added constraint / schematron rule)
* (number of examples provided via <exemplum>)
Finally, the resulting object is passed on to a d3.js component for visualization (Nick worked on that part)
Deliverables
Working document and notes: https://docs.google.com/document/d/1u77xtS1WncnkjCwR9CpTfOYeW65q7meaXz7PM-Y5Tno/edit#heading=h.6w2vysqik2f4
ODD being visualized (prepared by James Cummings): https://github.com/raffazizzi/Hackathon/blob/master/odd/test-odds/james.odd
Findings / goal
ODD is difficult and associate with advanced TEI users. But it needs to be the gateway to TEI and a constant companion to the life of a TEI project. We’ve been trying to figure out whether visualization can make ODD clearer and less daunting. Hard to tell with our simple visualization, but I think we had a consensus in the group that this is the way forward.
Not neglecting the power users, we think that visualizing ODDs can also help understanding other people’s usage of TEI, particularly when operating on a corpus created by someone else (cfr. Syd Bauman’s concept of “blind interchange“).
What did I learn
I learned that there is willingness to make ODD more accessible across the board; that the official JSON conversion from ODD needs improvement; and that underscore.js has some nice functional methods to deal with collections.
TEI Hackathon: Report by Nick Laiacona
Name:
Nick Laiacona, Performant Software Solutions LLC (www.performantsoftware.com)
Working Group Project:
I worked on the ODD Visualizer project.
Contribution to Group Project:
I adapted the D3 Tree View to work with the data model we developed to characterize the changes to a schema prescribed by a given ODD.
Methodology:
We made use of D3.js, underscore.js, Git Hub, Google Docs. Links to Git repo and our working document are on the TEI Hackathon Wiki page.
Conclusions:
(i): Deliverable(s)
We produced a working D3 visualization (http://tei.it.ox.ac.uk/Hackathon/odd/visualizer/index.html) and source code for it which is found on GitHub.
(ii): Findings
For me, I didn’t have a specific research question that was addressed by this activity, but nevertheless it was quite worthwhile.
(iii): Learning Outcomes
I think it was very useful to learn more about ODD structure and capabilities from the experts.
BaseX 7.9: The Summer Edition
Dear XML aficionados,
in the midst of summertime, we provide you with a new version of BaseX,
our XML database system and XQuery 3.0 processor. This is what you get:
Edirom Summer School 2014 – Course Program and Registration
Dear colleagues,
please let me inform you about the course program and registration deadline (31 July 2014) of this year’s Edirom-Summer-School (ESS), which will take place 8 to 12 September 2014 at the Heinz Nixdorf Institute (University of Paderborn, Germany). ESS is co-organized by the Virtual Research Group Edirom (University of Paderborn) and the german eHumanities project DARIAH-DE.
Continue reading “Edirom Summer School 2014 – Course Program and Registration”
Call for TAPAS project early adopters
The project developers for the TEI Archiving, Publishing, and Access Service (TAPAS) are still seeking TEI project teams to participate as early adopters of the TAPAS service for the next phase of project development.
TAPAS Project Background
TAPAS is the TEI Archiving, Publishing, and Access Service for scholars and other creators of TEI data who need a place to publish their materials in different forms and ensure it remains accessible over time. TAPAS also provides a support community of other project developers and TEI experts enthusiastic about sharing their technical and experiential knowledge of all things TEI.
We invite you to visit tapasproject.org/ for more information on the project, its development, and participation opportunities.
Early Adopter Phase of TAPAS
We are currently transitioning out of the beta testing phase of the project and into an important next phase where we are inviting TEI project teams to begin using the TAPAS service and contribute real projects and collections to the site. By “real” projects and collections, we mean full-fledged TAPAS projects and collections built with non-test TEI data that can remain as live projects on the TAPAS site once TAPAS goes public. As a note, your TEI data need not be fully complete, as your projects will necessarily be works in progress, but this data should not be test or placeholder data.
By launch time, we would like to have at least 35 projects visible with working collections, metadata, and TEI data. Your contributed projects will help demonstrate for future users the capabilities and value of the TAPAS service, and provide a more welcoming environment for people to join. As an early adopter, you will have the wonderful opportunity to showcase your work. Your project would be featured in TAPAS publicity and would receive high visibility as a featured project on the TAPAS site.
Becoming a TAPAS Early Adopter
If you are interested in serving as an early adopter, here’s what we would need you to do:
- Email us (info@tapasproject.org) and we will forward you information on how to access the TAPAS site and create an account
- create a new TAPAS project with full project information (description, logo, one or more project participants)
- create at least one TAPAS collection with full collection information (description, metadata, publication settings)
- upload one or more TEI files for that collection with full metadata, ideally including some fairly detailed subject and genre metadata
In order to participate, you will need to have a current TEI membership, either as an individual ($50) or through your institution. Membership provides critical support for both the TEI and TAPAS, so we hope you may consider joining or rejoining if you’re not currently a TEI member.
We hope very much that you will be able to join the TAPAS community of early adopters–if you are able to, please respond to info@tapasproject.organd we will send you more details about how to proceed.
Sincerely,
Ben
Benjamin J. Doyle
TAPAS Project Manager
Northeastern University
Email: Info@tapasproject.org
Twitter: @TAPAS_Project