The Development and Structure of the Encoded Archival Description (EAD) Document Type Definition

2001 ◽  
Vol 4 (3-4) ◽  
pp. 27-59 ◽  
Author(s):  
Janice E. Ruth
Keyword(s):  
Archival Description ◽  
Document Type Definition ◽  
Document Type ◽  
Type Definition

Encoded archival description (EAD) conversion: a methodological proposal

2000 ◽  
Vol 18 (4) ◽  
pp. 360-368
Author(s):  
Eduardo Peis ◽  
Félix de Moya ◽  
J. Carlos Fernández‐Molina
Keyword(s):  
Archival Description ◽  
Document Type Definition ◽  
Markup Language ◽  
Document Type ◽  
Digital Version ◽  
International Diffusion ◽  
Descriptive Information ◽  
Type Definition ◽  
Finding Aids ◽  
Methodological Strategy

The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language (SGML), document type definition (DTD) for archival description known as encoded archival description (EAD) is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version.

XML Documents Normalization Using GN-DTD

2013 ◽  
pp. 54-77
Author(s):  
Zurinahni Zainol ◽  
Bing Wang
Keyword(s):  
Normal Forms ◽  
Document Type Definition ◽  
Document Type ◽  
Graphical Notation ◽  
Xml Documents ◽  
Type Definition ◽  
Xml Document ◽  
Multiple Levels ◽  
Normalization Process

Designing a well-structured XML document is important for the sake of readability, maintainability and more importantly to avoid both data redundancies and update anomalies. This paper proposes to improve and simplify XML structural design using a normalization process. To achieve this, Graphical Notation for Document Type Definition (GN-DTD) is used to describe the structure of XML document at the schema level. Multiple levels of normal forms for GN-DTD are proposed and the corresponding normalization rules to transform from poorly designed into well-designed XML documents. A case study is presented to show the application of these normal forms and normalization algorithm.

DocBook

2018 ◽  
Author(s):  
Norman Walsh
Keyword(s):  
General Purpose ◽  
Xml Schema ◽  
Document Type Definition ◽  
Free Software ◽  
Computer Hardware ◽  
General Notion ◽  
Document Type ◽  
Active Maintenance ◽  
Type Definition

DocBook is a general purpose XML schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications). DocBook has been under active maintenance for more than 20 years,; it began life as an SGML document type definition. Because it is a large and robust schema, and because its main structures correspond to the general notion of what constitutes a “book,” DocBook has been adopted by a large and growing community of authors writing books of all kinds. DocBook is supported “out of the box” by a number of commercial tools, and there is rapidly expanding support for it in a number of free software environments. These features have combined to make DocBook a generally easy to understand, widely useful, and very popular schema. Dozens of organizations are using DocBook for millions of pages of documentation, in various print and online formats, worldwide.

scholarly journals Ontologías para sistemas mediadores

TecnoLógicas ◽  
2005 ◽  
pp. 9
Author(s):  
Gloria L. Giraldo-Gómez
Keyword(s):  
Document Type Definition ◽  
Document Type ◽  
Type Definition

En el contexto de la informática, los sistemas mediadores son definidos como «unos programas de computador (software) que explotan el conocimiento relativo a un conjunto de datos para crear información destinada a las aplicaciones de los usuarios» (Wiederhold, 1992). El objetivo de los mediadores es simplificar, abstraer, reducir, integrar y combinar datos que se encuentran en fuentes diferentes , para responder mejor a las consultas de los usuarios. Un sistema mediador es específico a un dominio de aplicación, éste es descrito por un esquema llamado esquema global u ontología del dominio. El rol de la ontología es central, ya que es el soporte para la expresión de las consultas (queries) de los usuarios. Igualmente, es a través de este esquema que las distintas fuentes de datos se interconectan. La construcción automatizada de los sistemas mediadores puede ser abordada, en un principio, automatizando la construcción de una parte fundamental de estos sistemas, como es la ontología. La proposición de métodos y técnicas para construir, lo más automáticamente posible. una ontología de dominio para un sistema mediador, es el tema de la investigación que se llevó a cabo en el marco de una tesis doctoral, en el LRI (Laboratoire de Recherche en Informatique) de la Universidad Paris Sur XI (Orsay-Francia). La solución propuesta está compuesta de tres etapas: extracción de los elementos que componen la ontología, a partir de un conjunto de DTDs (Document Type Definition), la estructuración de los elementos extraídos y la representación de estos elementos. Las técnicas propuestas han sido implementadas en un sistema llamado Ontol\Iedia. El objetivo de este artículo es mostrar los primeros resultados de dicha investigación. Debido a limitaciones de espacio, se presentarán la primera y segunda etapa. La tercera será el objeto de una próxima publicación. Dado que las ontologías tienen actualmente gran aplicabilidad, dejan muchos temas abiertos para la investigación. Como una consecuencia de este hecho estamos desarrollando una sublínea adscrita al grupo de investigación en integración de soluciones con tecnologías de información y comunicación -GIT del INSTITUTO TECNOLÓGICO METROPOLITANO. Los aspectos importantes que justifican el continuar investigando en este campo son introducidos en la parte final de este artículo.

Design and Implementation of a MEMS Design Process Description Language- MDPDL

2009 ◽  
Vol 16-19 ◽  
pp. 358-362
Author(s):  
Xiang Tong Yan ◽  
Ping Yu Jiang
Keyword(s):  
Design Process ◽  
Mechanical Design ◽  
Design Flow ◽  
Document Type Definition ◽  
Trial And Error ◽  
Description Language ◽  
Time To Market ◽  
Document Type ◽  
Design And Implementation ◽  
Type Definition

For the complexity and miniaturization of MEMS, MEMS design process is extremely different from general mechanical design process. Commonly the design flow is dominated by “trial-and-error” methods. It is necessary to describe design process of MEMS for reuse. This will help to reduce the number of redesigns and thus decrease the time to market. Based on XML and necessary extensions being made, a MEMS design process description language, called MDPDL, is presented and the syntax and implementation are discussed in detail. The Document Type Definition (DTD) is adopted to define the syntax rules for the tags of MDPDL, considering core activities and related resources of MEMS design process. Finally, an implementation case has been given out to illustrate the efficiency of MDPDL.

Sign in / Sign up

Export Citation Format

Share Document