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
Document ID: TECH-ANL-2024-011 Version: 1.0 Date: October 26, 2024 Author: Security & Architecture Team Status: Final 1. Executive Summary remoting-core.dll is a critical system library associated with .NET Remoting , a legacy Microsoft communication framework designed for cross-application domain, process, or machine communication. It is native (unmanaged) code, acting as a performance-critical bridge between the Common Language Runtime (CLR) and the managed .NET Remoting system.
| Risk Area | Description | Severity | | :--- | :--- | :--- | | | Malformed binary payloads can trigger memory corruption in unmanaged buffer handling. | Critical | | Type Confusion | Attackers may spoof object types during cross-domain transitions, leading to arbitrary code execution. | High | | Identity Elevation | Improper propagation of WindowsIdentity tokens could allow privilege escalation. | High | | Denial of Service | Crafted messages cause infinite loops or massive memory allocations in native buffers. | Medium | remoting-core.dll
Conduct an immediate audit to identify any production systems still using .NET Remoting. Classify such systems as technical debt and schedule remediation. For new development, do not reference or depend on this DLL. Prepared by: [Your Name/Team] Next Review Date: [Date + 6 months] or upon discovery of a new .NET Framework deserialization CVE. Document ID: TECH-ANL-2024-011 Version: 1
High. Requires significant code changes as the programming model differs fundamentally (proxies vs. service contracts). 9. Conclusion remoting-core.dll is a legacy but stable component that provides essential low-level plumbing for .NET Remoting. While functional, its exposure of unmanaged serialization handling makes it a security liability in modern applications. Organizations should prioritize migrating away from any system that loads this DLL, especially if remoting channels are exposed across network boundaries. | Risk Area | Description | Severity |