CC-BY
this specification document is based on the
EAD stands for Encoded Archival Description, and is a non-proprietary de facto standard for the encoding of finding aids for use in a networked (online) environment. Finding aids are inventories, indexes, or guides that are created by archival and manuscript repositories to provide information about specific collections. While the finding aids may vary somewhat in style, their common purpose is to provide detailed description of the content and intellectual organization of collections of archival materials. EAD allows the standardization of collection information in finding aids within and across repositories.
The specification of EAD with TEI ODD is a part of a real strategy of defining specific customisation of EAD that could be used at various stages of the process of integrating heterogeneous sources.
This methodology is based on the specification and customisation method inspired from the long lasting experience of the Text Encoding Initiative (TEI) community. In the TEI framework, one has the possibility of model specific subset or extensions of the TEI guidelines while maintaining both the technical (XML schemas) and editorial (documentation) content within a single framework.
This work has lead us quite far in anticipating that the method we have developed may be of a wider interest within similar environments, but also, as we imagine it, for the future maintenance of the EAD standard. Finally this work can be seen as part of the wider endeavour of European research infrastructures in the humanities such as CLARIN and DARIAH to provide support for researchers to integrate the use of standards in their scholarly practices. This is the reason why the general workflow studied here has been introduced as a use case in the umbrella infrastructure project Parthenos which aims, among other things, at disseminating information and resources about methodological and technical standards in the humanities.
We used ODD to encode completely the EAD standard, as well as the guidelines provided by the Library of Congress.
The EAD ODD is a XML-TEI document made up of three main parts. The first one is,
like any other TEI document, the
I also seek the structure and mentorship that a bootcamp provides. While self-study through platforms like Hack The Box and TryHackMe has given me foundational knowledge, I lack the guided, real-world scenarios and the collaborative feedback loop that comes from a cohort of peers and experienced instructors. I want to learn not just the "how" of a buffer overflow or a SQL injection, but the "why" behind prioritising risks and communicating findings to non-technical stakeholders. Furthermore, I am committed to the professional ethics that underpin this field: obtaining explicit permission, respecting scope, protecting data, and leaving every system as secure—or more secure—than I found it.
In the digital age, the line between guardian and invader is often drawn not by skill, but by intent. For years, popular culture has painted the hacker as a hooded figure in a dark room, a saboteur of systems. Yet, as I have learned more about the architecture of the internet, I have come to see a different figure: the ethical hacker. It is this role—part detective, part architect, and part protector—that draws me to the Ethical Hacking and Penetration Testing Bootcamp. My goal is not merely to learn how to break into systems, but to master the discipline of fortifying them against those who would do harm. Ethical Hacking and Penetration Testing Bootcam...
My initial interest in cybersecurity was born from a moment of vulnerability. Witnessing a small family business fall victim to a ransomware attack, I saw not just the financial loss, but the erosion of trust and the months of recovery that followed. The attackers exploited a simple, unpatched vulnerability—a mistake that could have been caught by a proactive defender. That event transformed my casual curiosity about computers into a focused mission. I realized that to defend effectively, one must first learn to think like the adversary. This is the core of penetration testing: authorized, simulated attacks designed to find and fix cracks before the real storm hits. I also seek the structure and mentorship that
I understand that ethical hacking is far more than running automated scripts. It is a rigorous, methodical discipline that sits at the intersection of technical depth and ethical clarity. The bootcamp’s emphasis on hands-on labs, industry-standard tools (such as Nmap, Wireshark, and Metasploit), and methodologies like the OWASP Testing Guide aligns perfectly with how I learn best—by doing, failing, and iterating. I am eager to move beyond theoretical knowledge and into live, controlled environments where I can practice reconnaissance, enumeration, exploitation, and reporting. The reporting phase, in particular, fascinates me; a penetration test is only as valuable as the actionable intelligence it provides to defenders. Furthermore, I am committed to the professional ethics
Beyond the Firewall: My Path to Ethical Hacking