0622074bdbaf9a94ec854fd96b987f9c.ppt
- Количество слайдов: 21
SGML, XML and the Kona Architecture
What is SGML? -- An Acronym z. Standard - International standard ISO-8879 z. Generalized - Not tied to a single machine, platform or system z. Markup - Describes information about the content of a document z. Language - Definitions of the structure of the document contains can be written
What SGML Provides z a list of elements which appear in a document za specification of the order and frequency in which these elements appear in the document (DTD) za verification that the marked up document conforms to the specification (parsers or validations)
Elements z. Elements are delimited with start tags and end tags Content Start tag End tag
Attribute Syntax Attributes immediately are specified after the element they are associated with Start tag Attribute Content End tag
What’s a DTD ? z. Document Type Definition z. Describes the structure of the document y. The names of allowable elements ythe content of each element type ythe structure of the document including xthe order in which elements must appear xhow often elements can appear ythe properties of the elements (attributes)
What is the Difference between HTML and SGML? z. Hyper. Text Markup Language (HTML) z. An application of SGML z. A DTD for authoring documents to be distributed via the World Wide Web z. Formats documents for viewing on a computer screen
Why not use HTML? z. Does not offer a rich tag set z. No mechanism to structure documents in a clinical manner z. Instable as a standard z. Delivery format not a collection technology z. Loose document type
What is XML? ze. Xtensible Markup Language (XML) z. XML = SGML with a few exceptions: y. A DTD is not required y. Provides stylesheets for presentation in a web browser (XSL) y. Some SGML syntax is not supported y. Designed for simple processing of diverse types of documents and data
The Role of XML z. When HTML does not meet the needs z. When collection of information is required z. When information resources are of long term value z. When there are complex relationships between information resources (links)
What is the KONA Proposal? z. Proposal z. Architecture that allows for varying levels of complexity in clinical documents z. Interface that is a mediator between two applications or systems z. Exchange mechanism from a document centered perspective with varying levels of requirements
The Kona Architecture z. Multi-layered schema consisting of three layers z. A basic, abstract layer to exchange narrative documents (Prose. Doc) z. A layer that provides simple classification (Clinical. Content) z. A layer that requires greater clincical semantics
The KONA Architecture
Moving Boxes z. Content: shoes z. My Label: Master Bedroom Closet: slippers, running shoes, hiking boots z. Foreman Mover’s Label: First Upstairs Right Room z. Actual Mover’s Label: Upstairs
A Transformation Architectural Forms specify how tags are changed: APPLICATION KONA Transform
SGML Architectures SGML architectures facilitate exchange between SGML documents & differing DTDS y. Organizations will most likely create their own DTDs to best meet their needs y. Semantics vary by granularity, localization, and specialization
Kona Design Assumptions z. Kona builds on HL 7; 2. 3 used for proposal z. Documents contain narrative text and data (codes) z. Not all clinical documents require the same degree of codes or markup
Flexible exchange: an oxymoron? z. Central dilemma of all information exchange standards: zlocal diversity, responsive to change zglobal rigidity, resistive to change z. How to provide extensible, flexible framework for information, yet retain the ability to exchange it freely?
Flexible exchange: Kona methodology z. Provide central information model : RIM + Meta DTDs z. Provide context for narrative text z. Development not required for mapping from local/specialized model to exchange model