#33820
Syntax, Semantics and Standards: Model for a National Health Information Network
This presentation will describe the National Health Information Network activity and role of syntax and semantics in building an interoperable framework for healthcare information on a national level.
Alschuler, Liora. IDEAlliance (2005). Articles>Information Design>Standards>Semantic
#33831
During the past twenty years, a huge number of custom languages - at least hundreds, perhaps a couple of thousand - have been attempted. Almost all have been miserable failures. That is to say, the vast majority have failed to achieve wide adoption, and those that were adopted have often failed to achieve their goals, whether of reducing costs, enriching applications, or both.
Bray, Tim. IDEAlliance (2005). Articles>Information Design>XML>Standards
#33835
As world events and business opportunities collide, the requirements for interoperable document formats become increasingly evident. Mandating XML for systems is a first step, but real information can't be shared effectively without a common understanding on the semantics and usage of the markup. One solution is to use agreed-on custom schemas. Another is to cite well-standardized formats such as XHTML, or deploy more specific XML formats such as Microsoft Office XML or the OpenDocument Format. None of these latter formats were written with a particular semantic usage in mind. They are of more general applicability than custom-built schemas, can be used for human-readable documents, and can be built into specific tools.
Bullard, C. Len. IDEAlliance (2005). Articles>Information Design>Standards>XML
#33902
XML schema analysis aims to extract quantitative and qualitative information from actual XML schemas. To this end, XML schemas are measured through systematic algorithms, on the basis of the intrinsic feature model of the XSD language. XML schema analysis is a derivative of software analysis (program analysis) and of software code metrics, in particular. The present article introduces essential concepts of XML schema analysis and applies them to the important problem of understanding XML schema usage in practice. Analyses for feature counts, idiosyncrasy counts, size metrics, complexity metrics, and XML schema styles are executed on a large corpus of real-world XML schemas.
Lammel, Ralf, Stan Kitsis and Dave Remy. IDEAlliance (2005). Articles>Information Design>Standards>XML
#33980
Daddy? Where Do Schemas Come From? Some Facts of Life for Schema Users
The rules for finding schema components when validating a document using W3C's XML Schema 1.0 are widely misunderstood. This presentation will the rules for constructing a schema and describe the reasoning behind the design.
Sperberg-McQueen, C.M. XML 2006 (2006). Articles>Information Design>XML>Standards
#33993
Lessons Learned: Development from Initial Planning to Successful Implementation
From initial data modeling, to technical XML Schema design and critical programmatic realization, we have an actionable, real-world set of comprehensive recommendations that can help you formulate a successful XML implementation.
Utzinger, Melissa and Cheryl Connors. XML 2006 (2006). Articles>Information Design>XML>Standards
#35165
In his article in this issue, Peter-Paul Koch proposes adding custom attributes to form elements to allow triggers for specialized behaviors. The W3C validator won’t validate a document with these attributes, as they aren’t part of the XHTML specification. This article will show you how to create a custom DTD that will add those custom attributes, and will show you how to validate documents that use those new attributes.
Eisenberg, J. David. List Apart, A (2009). Articles>Information Design>Standards>XML
#35371
DITA 1.2 Feature Description: Glossary and Terminology Specialization
In technical writing, synonyms and variants should be used judiciously and often avoided altogether. The use of one term consistently to express a given concept is preferred so that communication is clear and so that translation costs are minimized. For this reason, when synonyms and variants do exist in popular usage, it is common practice in commercial environments to choose one of the terms as the “preferred term.” This indicator of preferred usage needs to be documented in glossaries. Due to the limitations of markup languages for creating glossaries, usually the so-called preferred term is identified simply by making it the headword in a glossary entry and providing a definition in this glossary entry.
Warburton, Kara. OASIS (2009). Articles>Information Design>Standards>DITA
