Stage 3 proposal: Feature #13102 (Release Management Domain)
|
|
- Justin Tate
- 8 years ago
- Views:
Transcription
1 Stage 3 proposal: Feature #13102 (Release Management Domain)
2 Contents 2 Contents Stage 3 proposal: Feature #13102 (Release Management Domain)... 3 Structural implementation...3 Listing: releasemanagement.dtd... 4 Listing: releasemanagementdomain.ent... 8 Listing: releasemanagementdomain.mod... 8 Specification documentation...13 Changes to the architectural specification...13 Changes to the language specification... 15
3 Stage 3 proposal: Feature #13102 (Release Management Domain) 3 Stage 3 proposal: Feature #13102 (Release Management Domain) This proposal defines a release management domain for DITA 1.3 that enables content workers to log comments and metadata at the topic level when changes are made. The model for this domain comes from bookmap s <bookchangehistory, with modifications. This proposal seeks to add elements only; no processing is requested. Champion Tom Cihak (tom.cihak@freescale.com) is champion of this proposal, on behalf of the Technical Communications Subcommittee. Tracking information Event Date Links Stage 1 proposal accepted Feb 21, 2012 Minutes from 21 Feb 2012 Stage 2 proposal submitted Aug 23, 2013 Sep 4, 2013 Stage 2 proposal discussed Aug 20, 2013 Aug 27, 2013 Sep 3, 2013 DITA HTML download.php/50445/minutes txt download.php/50502/minutes txt download.php/50570/minutes txt Stage 2 proposal approved Sep 10, download.php/50716/minutes txt Stage 3 proposal submitted to reviewers Include s of reviewers Stage 3 proposal (this document) submitted Approved technical requirements As presented in the stage 2 proposal, this domain is to be implemented as elements only; no processing is requested. All DTD changes are detailed later in this document. Dependencies or interrelated proposals None, though any proposed changes to the content model of <data would have an impact on these elements. Structural implementation This proposal introduces a new release management domain. The top-level domain element is specialized from <metadata; therefore, it can only be included where that element is permissible. The intent is to include the domain within <prolog. Listings of the DTD and its two supporting entity files follow. Corresponding XML Schema files will also be required.
4 Stage 3 proposal: Feature #13102 (Release Management Domain) 4 Listing: releasemanagement.dtd <?xml version="1.0" encoding="utf-8"? <!-- HEADER -- <!-- MODULE: DITA Topic with release management domain integrated -- <!-- VERSION: <!-- DATE: August, <!-- -- <!-- PUBLIC DOCUMENT TYPE DEFINITION -- <!-- TYPICAL INVOCATION -- <!-- -- <!-- Refer to this file by the following public identifier or an appropriate system identifier -- <!-- The public ID above refers to the latest version of this DTD. To refer to this specific version, you may use this value: PUBLIC "-//OASIS//DTD DITA 1.2 Topic//EN" -- <!-- SYSTEM: Darwin Information Typing Architecture (DITA) -- <!-- -- <!-- PURPOSE: DTD to describe DITA Topics -- <!-- -- <!-- ORIGINAL CREATION DATE: -- <!-- March <!-- -- <!-- (C) Copyright OASIS Open 2005, <!-- (C) Copyright IBM Corporation 2001, <!-- All Rights Reserved. -- <!-- -- <!-- UPDATES: -- <! RDA: Added indexing domain -- <! RDA: Added props attribute extensions -- <! EK: Reformatted DTD modules for DITA <! RDA: Modify imbeds to use specific 1.2 version -- <! RDA: Added hazard domain -- <!-- TOPIC ENTITY DECLARATIONS -- <!-- DOMAIN ENTITY DECLARATIONS -- <!ENTITY % relmgmt-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.3 Release Management Domain//EN" "../org.oasis-open.release-management.doctypes/dtd/ releasemanagementdomain.ent" %relmgmt-d-dec; <!ENTITY % hi-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 Highlight Domain//EN"
5 Stage 3 proposal: Feature #13102 (Release Management Domain) 5 "../../base/dtd/highlightdomain.ent" %hi-d-dec; <!ENTITY % ut-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 Utilities Domain//EN" "../../base/dtd/utilitiesdomain.ent" %ut-d-dec; <!ENTITY % indexing-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 Indexing Domain//EN" "../../base/dtd/indexingdomain.ent" %indexing-d-dec; <!ENTITY % hazard-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 Hazard Statement Domain//EN" "../../base/dtd/hazardstatementdomain.ent" %hazard-d-dec; <!ENTITY % abbrev-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 Abbreviated Form Domain//EN" "abbreviatedomain.ent" %abbrev-d-dec; <!ENTITY % pr-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 Programming Domain//EN" "programmingdomain.ent" %pr-d-dec; <!ENTITY % sw-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 Software Domain//EN" "softwaredomain.ent" %sw-d-dec; <!ENTITY % ui-d-dec PUBLIC "-//OASIS//ENTITIES DITA 1.2 User Interface Domain//EN" "uidomain.ent" %ui-d-dec; <!-- DOMAIN ATTRIBUTE DECLARATIONS -- <!-- DOMAIN EXTENSIONS -- <!-- One for each extended base element, with the of the domain(s) in which the extension was declared -- <!ENTITY % pre "pre %pr-d-pre; %sw-d-pre; %ui-d-pre; " <!ENTITY % keyword "keyword %pr-d-keyword; %sw-d-keyword; %ui-d-keyword;
6 Stage 3 proposal: Feature #13102 (Release Management Domain) 6 " <!ENTITY % ph "ph %hi-d-ph; %pr-d-ph; %sw-d-ph; %ui-d-ph; " <!ENTITY % term "term %abbrev-d-term; " <!ENTITY % fig "fig %pr-d-fig; %ut-d-fig; " <!ENTITY % dl "dl %pr-d-dl; " <!ENTITY % index-base "index-base %indexing-d-index-base; " <!ENTITY % note "note %hazard-d-note; " <!ENTITY % metadata "metadata %relmgmt-d-metadata; " <!-- DOMAIN ATTRIBUTE EXTENSIONS -- <!ENTITY % props-attribute-extensions "" <!ENTITY % base-attribute-extensions "" <!-- TOPIC NESTING OVERRIDE -- <!-- Redefine the infotype entity to exclude other topic types and disallow nesting -- <!ENTITY % topic-info-types "topic " <!-- DOMAINS ATTRIBUTE OVERRIDE -- <!-- Must be declared ahead of the DTDs, which first in order -- <!ENTITY included-domains "&hi-d-att; &ut-d-att; &indexing-d-att; &hazard-d-att; &abbrev-d-att; &pr-d-att; &sw-d-att;
7 Stage 3 proposal: Feature #13102 (Release Management Domain) 7 " &ui-d-att; &relmgmt-d-att; <!-- TOPIC ELEMENT INTEGRATION -- <!-- Embed topic to get generic elements -- <!ENTITY % topic-type PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Topic//EN" "../../base/dtd/topic.mod" %topic-type; <!-- DOMAIN ELEMENT INTEGRATION -- <!ENTITY % relmgmt-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.3 Release Management Domain//EN" "../org.oasis-open.release-management.doctypes/dtd/ releasemanagementdomain.mod" %relmgmt-d-def; <!ENTITY % hi-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Highlight Domain//EN" "../../base/dtd/highlightdomain.mod" %hi-d-def; <!ENTITY % ut-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Utilities Domain//EN" "../../base/dtd/utilitiesdomain.mod" %ut-d-def; <!ENTITY % indexing-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Indexing Domain//EN" "../../base/dtd/indexingdomain.mod" %indexing-d-def; <!ENTITY % hazard-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Hazard Statement Domain//EN" "../../base/dtd/hazardstatementdomain.mod" %hazard-d-def; <!ENTITY % abbrev-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Abbreviated Form Domain//EN" "abbreviatedomain.mod" %abbrev-d-def; <!ENTITY % ui-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 User Interface Domain//EN" "uidomain.mod" %ui-d-def; <!ENTITY % pr-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Programming Domain//EN"
8 Stage 3 proposal: Feature #13102 (Release Management Domain) 8 "programmingdomain.mod" %pr-d-def; <!ENTITY % sw-d-def PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Software Domain//EN" "softwaredomain.mod" %sw-d-def; <!-- ================== End DITA Topic DTD ====================== -- Listing: releasemanagementdomain.ent <?xml version="1.0" encoding="utf-8"? <!-- ============================================================= DITA Release Management Metadata Domain Defines element types for capturing change details within topics or maps. DITA 1.3 Copyright (c) 2013 OASIS Open ============================================================= -- <!-- Release Management DOMAIN ENTITIES -- <!ENTITY % relmgmt-d-metadata "change-historylist " <!ENTITY relmgmt-d-att "(topic relmgmt-d)" <!-- ================== End Highlight Domain Entities ============ -- Listing: releasemanagementdomain.mod <!-- ============================================================= DITA Release Management Metadata Domain Defines element types for capturing change details within topics or maps. DITA 1.3 Copyright (c) 2013 OASIS Open ============================================================= -- <!ENTITY % change-historylist "change-historylist" <!ENTITY % change-item "change-item" <!ENTITY % change-person "change-person" <!ENTITY % change-organization "change-organization" <!ENTITY % change-revisionid "change-revisionid"
9 Stage 3 proposal: Feature #13102 (Release Management Domain) 9 <!ENTITY % change-request-reference "change-request-reference" <!ENTITY % change-started "change-started" <!ENTITY % change-completed "change-completed" <!ENTITY % change-summary "change-summary" <!ENTITY % change-request-system "change-request-system" <!ENTITY % change-request-id "change-request-id" <!-- Long Name: Change History List -- <!ENTITY % changehistory.data.atts %univ-atts; datatype #IMPLIED outputclass #IMPLIED <!ENTITY % change-historylist.content "(%change-item;)* " <!ENTITY % change-historylist.attributes %changehistory.data.atts; "change-historylist" <!ELEMENT change-historylist %change-historylist.content; <!ATTLIST change-historylist %change-historylist.attributes; <!-- Long Name: Change Item An individual release note. -- <!ENTITY % change-item.content "((%change-person; %change-organization;)*, %change-revisionid;?, %change-request-reference;?, %change-started;?, %change-completed;, %change-summary;?, %data;*) " <!ENTITY % change-item.attributes %changehistory.data.atts; "change-item" <!ELEMENT change-item %change-item.content; <!ATTLIST change-item %change-item.attributes; <!-- Long Name: Change Person: the person who made the change -- <!ENTITY % change-person.content "(#P text)*" <!ENTITY % change-person.attributes
10 Stage 3 proposal: Feature #13102 (Release Management Domain) 10 %changehistory.data.atts; "change-person" <!ELEMENT change-person %change-person.content; <!ATTLIST change-person %change-person.attributes; <!-- Long Name: Change Organization: the organization that instigated (required, suggested) the change -- <!ENTITY % change-organization.content "(#P text)*" <!ENTITY % change-organization.attributes %changehistory.data.atts; "change-organization" <!ELEMENT change-organization %change-organization.content; <!ATTLIST change-organization %change-organization.attributes; <!-- Long Name: Revision ID Specifies the revision ID to which the change applies. Revision IDs are normally specified within publication maps (e.g., Bookmap <revisionid element). -- <!ENTITY % change-revisionid.content "(%data.cnt;)*" <!ENTITY % change-revisionid.attributes %changehistory.data.atts; "change-revisionid" <!ELEMENT change-revisionid %change-revisionid.content; <!ATTLIST change-revisionid %change-revisionid.attributes; <!-- Long Name: Change Request Reference Provides traceablity to an external change request or other ticketing system; -- <!ENTITY % change-request-reference.content "(%change-request-system;?, %change-request-id;?)" <!ENTITY % change-request-reference.attributes %changehistory.data.atts; "change-request-reference" <!ELEMENT change-request-reference %change-request-reference.content; <!ATTLIST change-request-reference %change-request-reference.attributes;
11 Stage 3 proposal: Feature #13102 (Release Management Domain) 11 <!-- Long Name; Change Request System Some description of or identifier for the information system that manages or serves the referenced change request, for example, an issue tracking system. -- <!ENTITY % change-request-system.content "(%data.cnt;)*" <!ENTITY % change-request-system.attributes %changehistory.data.atts; "change-request-system" <!ELEMENT change-request-system %change-request-system.content; <!ATTLIST change-request-system %change-request-system.attributes; <!-- Long Name: Change request ID The identifier of the change request, such as an issue ID or ticket number. -- <!ENTITY % change-request-id.content "(%data.cnt;)*" <!ENTITY % change-request-id.attributes %changehistory.data.atts; "change-request-id" <!ELEMENT change-request-id %change-request-id.content; <!ATTLIST change-request-id %change-request-id.attributes; <!-- Long Name: Change started date -- <!ENTITY % change-started.content "(#P text)*" <!ENTITY % change-started.attributes %changehistory.data.atts; "change-started" <!ELEMENT change-started %change-started.content; <!ATTLIST change-started %change-started.attributes; <!-- Long Name: Change completed date -- <!ENTITY % change-completed.content "(#P text)*" <!ENTITY % change-completed.attributes %changehistory.data.atts;
12 Stage 3 proposal: Feature #13102 (Release Management Domain) 12 "change-completed" <!ELEMENT change-completed %change-completed.content; <!ATTLIST change-completed %change-completed.attributes; <!-- Long Name: Change Summary The portion of the release note that will/may appear in a document -- <!ENTITY % change-summary.content "(%data.cnt;)*" <!ENTITY % change-summary.attributes %changehistory.data.atts; "change-summary" <!ELEMENT change-summary %change-summary.content; <!ATTLIST change-summary %change-summary.attributes; <!-- SPECIALIZATION ATTRIBUTE DECLARATIONS -- <!ATTLIST change-historylist %global-atts; class "- topic/metadata rm-d/change-historylist " <!ATTLIST change-item %global-atts; class "- topic/data rm-d/change-item " <!ATTLIST change-person %global-atts; class "- topic/data rm-d/change-person " <!ATTLIST change-organization %global-atts; class "- topic/data rm-d/change-organization " <!ATTLIST change-revisionid %global-atts; class "- topic/data rm-d/change-revisionid " <!ATTLIST change-request-reference %global-atts; class "- topic/data rm-d/change-request-reference " <!ATTLIST change-started %global-atts; class "- topic/data rm-d/change-started " <!ATTLIST change-completed %global-atts; class "- topic/data rm-d/change-completed " <!ATTLIST change-summary %global-atts; class "- topic/data rm-d/change-summary " <!ATTLIST change-request-system %global-atts; class "- topic/data rm-d/change-request-system " <!ATTLIST change-request-id %global-atts; class "- topic/data rm-d/change-request-id " <!-- ============== End of Release Management domain ======================= --
13 Stage 3 proposal: Feature #13102 (Release Management Domain) 13 Specification documentation The release management domain requires changes to the architectural specification and to the language specification. Changes to the architectural specification The architectural specification requires a new topic describing release management. Release Management Domain The release management domain provides markup that enables content workers to log comments and metadata at the topic level when changes are made. Release notes To help customers locate significant changes in revisions of large documents, the release management domain provides markup to allow the addition of release notes at the topic level, elminating the need for separate release note topics or external files such as spreadsheets or databases. These release notes may be gathered from the topics of a publication by an external process and assembled into an appendix or separate document; no processing support is currently provided. Structure of the release management domain elements This section gives an overview of the release management elements and a brief description of each. This figure shows the structure of the release management elements. Figure 1: Release Management Elements Here is a brief description of each element: change-historylist change-item change-person change-organization change-revisionid change-request-reference change-request-system contains a number of release notes (change-item) applicable to the topic contains a single release note. It contains information about when and by whom the topic was edited during its history. contains the of a person who made the change described by the release note. contains the of a person who made a change described by the release note. contains contains elements that link the change described by the release note to an external system contains the of the external system being referenced
14 Stage 3 proposal: Feature #13102 (Release Management Domain) 14 change-request-id change-started change-completed change-summary contains an ID or other reference number used by the external system contains a string date, with optional time and time zone, that represents the date/time work started on the change described by the release note. contains a string date, with optional time and time zone, that represents the date/time work on the change described by the release note was finished contains a summary description of the change described by the release note Here are example release notes: This figure shows three simple release notes added to a single topic. This topic is used in documentation for two products, A and B. <prolog... <changehistory-list <change-item product="producta productb" <change-persontom Cihak</change-person <change-completed </change-completed <change-summarymade change 1 to both products</changesummary <datadetails of change 1</data </change-item <change-item product="producta" <change-persontom Cihak</change-person <change-completed </change-completed <change-summarymade change 2 to product A</change-summary <datadetails of change 2</data </change-item <change-item product="producta productb" <change-persontom Cihak</change-person <change-completed </change-completed <change-summarymade change 3 to both products</changesummary <datadetails of change 3</data </change-item </changehistory-list... </prolog Figure 2: Excerpt from prolog of topic mytopic Modules The following DITA modules are provided for the release management domain: releasemanagementdomain.mod. releasemanagementdomain.ent releasemanagementdomainmod.xsd, releasemanagementdomaingrp.xsd
15 Stage 3 proposal: Feature #13102 (Release Management Domain) 15 Changes to the language specification The language specification requires new topics for each of the new elements introduced by the release management domain. In addition, the <prolog topic must be modified to show an additional element, <change-historylist. prolog The <prolog element... Changes to prolog element Update <prolog to show new child element, <change-historylist, as follows: Table 1: Changes to <prolog Section Doctypes DITA 1.2 Text Proposed 1.3 Text Modified topic, concept, ditabase, glossary, glossentry, glossgroup, reference, task, machinerytask learningassessment, learningcontent, learningoverview, learningplan, learningsummary ( (author) (any number) then (source) (optional) then (publisher) (optional) then (copyright) (any number) then (critdates) (optional) then (permissions) (optional) then (metadata) (any number) then (resourceid) (any number) then (data or data-about or foreign or unknown) (any number) ) ( (author) (any number) then (source) (optional) then (publisher) (optional) then (copyright) (any number) then (critdates) (optional) then (permissions) (optional) then (metadata or lclom) (any number) then (resourceid) (any number) then (data or data-about or foreign or unknown) (any number) ) ( (author) (any number) then (source) (optional) then (publisher) (optional) then (copyright) (any number) then (critdates) (optional) then (permissions) (optional) then (metadata) (any number) then (resourceid) (any number) then (change-historylist) (optional) then (data or data-about or foreign or unknown) (any number) ) ( (author) (any number) then (source) (optional) then (publisher) (optional) then (copyright) (any number) then (critdates) (optional) then (permissions) (optional) then (metadata or lclom) (any number) then (resourceid) (any number) then (change-historylist) (optional) then (data or data-about or foreign or unknown) (any number) ) change-historylist The <change-historylist element provides a container to hold individual release notes (<change-item). It appears in the topic prolog.. <change-historylist contains these elements: change-item change-person change-organization change-revisionid change-request-reference change-request-system change-request-id change-started change-completed change-summary
16 Stage 3 proposal: Feature #13102 (Release Management Domain) 16 <prolog - topic/metadata rm-d/change-historylist This figure shows three simple release notes added to a single topic. This topic is used in documentation for two products, A and B. <prolog... <changehistory-list <change-item product="producta productb" <change-persontom Cihak</change-person <change-organizationjedec</change-organization <change-completed </change-completed <change-summarymade change 1 to both products</changesummary <datadetails of change 1</data </change-item <change-item product="producta" <change-persontom Cihak</change-person <change-completed </change-completed <change-summarymade change 2 to product A</change-summary <datadetails of change 2</data </change-item <change-item product="producta productb" <change-persontom Cihak</change-person <change-completed </change-completed <change-summarymade change 3 to both products</changesummary <datadetails of change 3</data </change-item </changehistory-list... </prolog Figure 3: Excerpt from prolog of topic mytopic change-item The <change-item element represents a record of a single topic change. <change-item may contain these elements: change-person change-organization change-revisionid change-request-reference change-started change-completed change-summary data
17 Stage 3 proposal: Feature #13102 (Release Management Domain) 17 Note: Each of these elements is optional. <change-historylist - topic/data rm-d/change-item See change-historylist on page 15. change-person The <change-person element holds the of the person making the change. <change-person has text content. <change-item - topic/data rm-d/change-person See change-historylist on page 15. change-organization The <change-organization element holds the of an organization that required the change. <change-organization has text content. <change-item - topic/data rm-d/change-organization See change-historylist on page 15.
18 Stage 3 proposal: Feature #13102 (Release Management Domain) 18 change-revisionid The <change-revisionid element contains a revision id string that can identify the change. <change-revisionid has text content. <change-item - topic/data rm-d/change-revisionid See change-historylist on page 15. change-request-reference The <change-request-reference element contains elements to link the change made to an external tracking system.. <change-request-reference may contain these elements: change-request-system change-request-id <change-item - topic/metadata rm-d/change-request-reference See change-historylist on page 15. change-request-system The <change-request-system element holds the of an external tracking system. <change-request-system has text content. <change-request-reference
19 Stage 3 proposal: Feature #13102 (Release Management Domain) 19 - topic/data rm-d/change-request-system See change-historylist on page 15. change-request-id The <change-request-id element holds the number of a ticket in an external tracking system. <change-request-id has text content. <change-request-reference - topic/data rm-d/change-request-id See change-historylist on page 15. change-started The <change-started element holds date on which the change was initiated. <change-started has text content. It is strongly recommended that the date strings used conform to the ISO 8601 standard (unless a Unix-style machine timestamp is used). The string may contain a date and time or just a date. <change-item - topic/data rm-d/change-started See change-historylist on page 15.
20 Stage 3 proposal: Feature #13102 (Release Management Domain) 20 change-completed The <change-completed element holds date on which the change was completed. <change-completed has text content. It is strongly recommended that the date strings used conform to the ISO 8601 standard (unless a Unix-style machine timestamp is used). The string may contain a date and time or just a date. <change-item - topic/data rm-d/change-completed See change-historylist on page 15. change-summary The <change-summary element a summary description of the change. <change-summary has text content. <change-item - topic/data rm-d/change-summary See change-historylist on page 15.
DITA 1.3 Feature Article: About the DITA 1.3 release management domain
An OASIS DITA Adoption Technical Committee Publication DITA 1.3 Feature Article: About the DITA 1.3 release management domain Author: Tom Cihak, Keith Schengili-Roberts On behalf of the DITA Adoption Technical
More informationManaging content for information centers and large repositories using the DITA framework
Managing content for information centers and large repositories using the DITA framework ABSTRACT Alice S. Etim Winston Salem State University DITA is an acronym for Darwin Information Typing Architecture.
More informationDTD Tutorial. About the tutorial. Tutorial
About the tutorial Tutorial Simply Easy Learning 2 About the tutorial DTD Tutorial XML Document Type Declaration commonly known as DTD is a way to describe precisely the XML language. DTDs check the validity
More informationLast Week. XML (extensible Markup Language) HTML Deficiencies. XML Advantages. Syntax of XML DHTML. Applets. Modifying DOM Event bubbling
XML (extensible Markup Language) Nan Niu (nn@cs.toronto.edu) CSC309 -- Fall 2008 DHTML Modifying DOM Event bubbling Applets Last Week 2 HTML Deficiencies Fixed set of tags No standard way to create new
More informationMadCap Software. Import Guide. Flare 11
MadCap Software Import Guide Flare 11 Copyright 2015 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software described in this document is furnished
More informationStructured Data Capture (SDC) Trial Implementation
Integrating the Healthcare Enterprise 5 IHE Quality, Research, and Public Health Technical Framework Supplement 10 Structured Data Capture (SDC) 15 Trial Implementation 20 Date: October 27, 2015 Author:
More informationIntroduction to XML. Data Integration. Structure in Data Representation. Yanlei Diao UMass Amherst Nov 15, 2007
Introduction to XML Yanlei Diao UMass Amherst Nov 15, 2007 Slides Courtesy of Ramakrishnan & Gehrke, Dan Suciu, Zack Ives and Gerome Miklau. 1 Structure in Data Representation Relational data is highly
More informationIntroduction to XML Applications
EMC White Paper Introduction to XML Applications Umair Nauman Abstract: This document provides an overview of XML Applications. This is not a comprehensive guide to XML Applications and is intended for
More informationQuiz! Database Indexes. Index. Quiz! Disc and main memory. Quiz! How costly is this operation (naive solution)?
Database Indexes How costly is this operation (naive solution)? course per weekday hour room TDA356 2 VR Monday 13:15 TDA356 2 VR Thursday 08:00 TDA356 4 HB1 Tuesday 08:00 TDA356 4 HB1 Friday 13:15 TIN090
More informationStructured vs. unstructured data. Semistructured data, XML, DTDs. Motivation for self-describing data
Structured vs. unstructured data 2 Semistructured data, XML, DTDs Introduction to databases CSCC43 Winter 2011 Ryan Johnson Databases are highly structured Well-known data format: relations and tuples
More informationAn Oracle White Paper March 2012. Managing Metadata with Oracle Data Integrator
An Oracle White Paper March 2012 Managing Metadata with Oracle Data Integrator Introduction Metadata information that describes data is the foundation of all information management initiatives aimed at
More informationContact Management. User Guide V3.0. Subject to change without prior notice. www.teczo.com
Contact Management V3.0 Subject to change without prior notice Table of Contents Table of Contents... 2 1.0 Module Overview... 3 2.0 Using the Module... 4 2.1 Contact Management Summary Page... 4 2.1.1
More informationExperiences with an XML topic architecture (DITA)
Experiences with an XML topic architecture (DITA) Don R. Day, IBM James H. (Jamie) Roberts, IBM WinWriters Conference February 12, 2002 Overview Brief history Lessons learned Top 10 benefits History: Darwin
More informationTerms and Definitions for CMS Administrators, Architects, and Developers
Sitecore CMS 6 Glossary Rev. 081028 Sitecore CMS 6 Glossary Terms and Definitions for CMS Administrators, Architects, and Developers Table of Contents Chapter 1 Introduction... 3 1.1 Glossary... 4 Page
More informationXML. CIS-3152, Spring 2013 Peter C. Chapin
XML CIS-3152, Spring 2013 Peter C. Chapin Markup Languages Plain text documents with special commands PRO Plays well with version control and other program development tools. Easy to manipulate with scripts
More informationIBM Unica emessage Version 8 Release 6 February 13, 2015. User's Guide
IBM Unica emessage Version 8 Release 6 February 13, 2015 User's Guide Note Before using this information and the product it supports, read the information in Notices on page 403. This edition applies to
More informationStandard Recommended Practice extensible Markup Language (XML) for the Interchange of Document Images and Related Metadata
Standard for Information and Image Management Standard Recommended Practice extensible Markup Language (XML) for the Interchange of Document Images and Related Metadata Association for Information and
More informationXML and Data Integration
XML and Data Integration Week 11-12 Week 11-12 MIE253-Consens 1 Schedule Week Date Lecture Topic 1 Jan 9 Introduction to Data Management 2 Jan 16 The Relational Model 3 Jan. 23 Constraints and SQL DDL
More informationStructured Data Capture (SDC) Draft for Public Comment
Integrating the Healthcare Enterprise 5 IHE Quality, Research, and Public Health Technical Framework Supplement 10 Structured Data Capture (SDC) 15 Draft for Public Comment 20 Date: June 6, 2014 Author:
More informationSoftware Design Document SAMLv2 IDP Proxying
Software Design Document SAMLv2 IDP Proxying Federation Manager 7.5 Version 0.2 Please send comments to: dev@opensso.dev.java.net This document is subject to the following license: COMMON DEVELOPMENT AND
More informationExtensible Markup Language (XML): Essentials for Climatologists
Extensible Markup Language (XML): Essentials for Climatologists Alexander V. Besprozvannykh CCl OPAG 1 Implementation/Coordination Team The purpose of this material is to give basic knowledge about XML
More informationApplication of XML Tools for Enterprise-Wide RBAC Implementation Tasks
Application of XML Tools for Enterprise-Wide RBAC Implementation Tasks Ramaswamy Chandramouli National Institute of Standards and Technology Gaithersburg, MD 20899,USA 001-301-975-5013 chandramouli@nist.gov
More information04 XML Schemas. Software Technology 2. MSc in Communication Sciences 2009-10 Program in Technologies for Human Communication Davide Eynard
MSc in Communication Sciences 2009-10 Program in Technologies for Human Communication Davide Eynard Software Technology 2 04 XML Schemas 2 XML: recap and evaluation During last lesson we saw the basics
More informationestatistik.core: COLLECTING RAW DATA FROM ERP SYSTEMS
WP. 2 ENGLISH ONLY UNITED NATIONS STATISTICAL COMMISSION and ECONOMIC COMMISSION FOR EUROPE CONFERENCE OF EUROPEAN STATISTICIANS Work Session on Statistical Data Editing (Bonn, Germany, 25-27 September
More informationHow To Use Xml In A Web Browser (For A Web User)
Anwendersoftware a Advanced Information Management Chapter 3: XML Basics Holger Schwarz Universität Stuttgart Sommersemester 2009 Overview Motivation Fundamentals Document Type Definition (DTD) XML Namespaces
More information10CS73:Web Programming
10CS73:Web Programming Question Bank Fundamentals of Web: 1.What is WWW? 2. What are domain names? Explain domain name conversion with diagram 3.What are the difference between web browser and web server
More informationWebSphere Business Monitor
WebSphere Business Monitor Monitor models 2010 IBM Corporation This presentation should provide an overview of monitor models in WebSphere Business Monitor. WBPM_Monitor_MonitorModels.ppt Page 1 of 25
More informationTranslation and Localization Services
Translation and Localization Services Company Overview InterSol, Inc., a California corporation founded in 1996, provides clients with international language solutions. InterSol delivers multilingual solutions
More informationChange Management Procedure For Increase Bandwidth to University Buildings Project
Change Management Procedure For Increase Bandwidth to University Buildings Project Version number 1.0 Draft as of 4/11/2011 Printed on 7/1/2011 Author William M. Jones Owner William M. Jones Change Management
More informationAppendix 2-A. Application and System Development Requirements
Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility
More informationNo Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
[MS-EDCSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationManagement and Web service Management
Management and Web service Management This presentation offers work to OASIS completed by IBM with contribution from CA and Talking Blocks The work details a frame of reference for Management Applications,
More informationChapter 3: XML Namespaces
3. XML Namespaces 3-1 Chapter 3: XML Namespaces References: Tim Bray, Dave Hollander, Andrew Layman: Namespaces in XML. W3C Recommendation, World Wide Web Consortium, Jan 14, 1999. [http://www.w3.org/tr/1999/rec-xml-names-19990114],
More informationSage CRM Connector Tool White Paper
White Paper Document Number: PD521-01-1_0-WP Orbis Software Limited 2010 Table of Contents ABOUT THE SAGE CRM CONNECTOR TOOL... 1 INTRODUCTION... 2 System Requirements... 2 Hardware... 2 Software... 2
More informationRepresentation of E-documents in AIDA Project
Representation of E-documents in AIDA Project Diana Berbecaru Marius Marian Dip. di Automatica e Informatica Politecnico di Torino Corso Duca degli Abruzzi 24, 10129 Torino, Italy Abstract Initially developed
More informationCommon definitions and specifications for OMA REST interfaces
Common definitions and specifications for OMA REST interfaces Candidate Version 1.0 11 Jan 2011 Open Mobile Alliance OMA-TS-REST_Common-V1_0-20110111-C OMA-TS-REST_Common-V1_0-20110111-C Page 2 (20) Use
More informationXML and Data Management
XML and Data Management XML standards XML DTD, XML Schema DOM, SAX, XPath XSL XQuery,... Databases and Information Systems 1 - WS 2005 / 06 - Prof. Dr. Stefan Böttcher XML / 1 Overview of internet technologies
More informationInformation and documentation The Dublin Core metadata element set
ISO TC 46/SC 4 N515 Date: 2003-02-26 ISO 15836:2003(E) ISO TC 46/SC 4 Secretariat: ANSI Information and documentation The Dublin Core metadata element set Information et documentation Éléments fondamentaux
More informationBACKGROUND. Namespace Declaration and Qualification
LOGISTICS MANAGEMENT INSTITUTE Recommended XML Namespace for Government Organizations GS301L1/AUGUST 2003 By Jessica L. Glace and Mark R. Crawford INTRODUCTION The Extensible Markup Language (XML) is rapidly
More informationResearch and Implementation of Single Sign-On Mechanism for ASP Pattern *
Research and Implementation of Single Sign-On Mechanism for ASP Pattern * Bo Li, Sheng Ge, Tian-yu Wo, and Dian-fu Ma Computer Institute, BeiHang University, PO Box 9-32 Beijing 100083 Abstract Software
More informationRotorcraft Health Management System (RHMS)
AIAC-11 Eleventh Australian International Aerospace Congress Rotorcraft Health Management System (RHMS) Robab Safa-Bakhsh 1, Dmitry Cherkassky 2 1 The Boeing Company, Phantom Works Philadelphia Center
More informationChapter 1: Introduction
Chapter 1: Introduction Database System Concepts, 5th Ed. See www.db book.com for conditions on re use Chapter 1: Introduction Purpose of Database Systems View of Data Database Languages Relational Databases
More informationOn XACML, role-based access control, and health grids
On XACML, role-based access control, and health grids 01 On XACML, role-based access control, and health grids D. Power, M. Slaymaker, E. Politou and A. Simpson On XACML, role-based access control, and
More informationStandard Registry Development and Publication Process
Document number: DSP4006 Date: 2007-12-12 Version: 1.1.0 Standard Registry Development and Publication Process Document type: Specification Document status: Informational Document language: E Copyright
More informationSAML V2.0 Asynchronous Single Logout Profile Extension Version 1.0
SAML V2.0 Asynchronous Single Logout Profile Extension Version 1.0 Committee Specification 01 22 November 2012 Specification URIs This version: http://docs.oasis-open.org/security/saml/post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-
More informationWeb Service Implementation Methodology
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 Web Service Implementation Methodology Public Review Draft 1.0, 05 September 2005
More informationCA Nimsoft Monitor. Probe Guide for NT Event Log Monitor. ntevl v3.8 series
CA Nimsoft Monitor Probe Guide for NT Event Log Monitor ntevl v3.8 series Legal Notices Copyright 2013, CA. All rights reserved. Warranty The material contained in this document is provided "as is," and
More informationArbortext 6.1. Curriculum Guide
Arbortext 6.1 Curriculum Guide Live Classroom Curriculum Guide Authoring using Arbortext Editor 6.1 Authoring for DITA using Arbortext Editor 6.1 Using Arbortext Styler 6.1 Authoring using Arbortext Editor
More informationCS 501- Software Engineering. Legal Data Markup Software DTD Design Document. Version 1.0
CS 501- Software Engineering Legal Data Markup Software DTD Design Document Version 1.0 Document Revision History Date Version Description Author 11/27/00 1.0 Draft for Delivery LDMS Team Confidential
More informationSAML Federated Identity at OASIS
International Telecommunication Union SAML Federated Identity at OASIS Hal Lockhart BEA Systems Geneva, 5 December 2006 SAML and the OASIS SSTC o SAML: Security Assertion Markup Language A framework for
More informationApplication Developer Guide
IBM Maximo Asset Management 7.1 IBM Tivoli Asset Management for IT 7.1 IBM Tivoli Change and Configuration Management Database 7.1.1 IBM Tivoli Service Request Manager 7.1 Application Developer Guide Note
More information[MS-CCEIP]: Corporate Customer Experience Improvement Program Client-to-Server Protocol
[MS-CCEIP]: Corporate Customer Experience Improvement Program Client-to-Server Protocol Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes
More informationHello World Portlet Rendered with JSP for WebSphere Portal Version 4.1
1 of 11 16.10.2002 11:41 Hello World Portlet Rendered with JSP for WebSphere Portal Version 4.1 Table of Contents Creating the directory structure Creating the Java code Compiling the code Creating the
More informationXML for Manufacturing Systems Integration
Information Technology for Engineering & Manufacturing XML for Manufacturing Systems Integration Tom Rhodes Information Technology Laboratory Overview of presentation Introductory material on XML NIST
More informationWhat's New In DITA CMS 4.0
What's New In DITA CMS 4.0 WWW.IXIASOFT.COM / DITACMS v. 4.0 / Copyright 2014 IXIASOFT Technologies. All rights reserved. Last revised: December 11, 2014 Table of contents 3 Table of contents Chapter
More informationXML Implementation Guide: General Information
: General Information Copyright 2000 Mortgage Industry Standards Maintenance Organization (MISMO). All rights reserved Permission to use, copy, modify, and distribute the MISMO DTD and its accompanying
More informationRational Rational ClearQuest
Rational Rational ClearQuest Version 7.0 Windows Using Project Tracker GI11-6377-00 Rational Rational ClearQuest Version 7.0 Windows Using Project Tracker GI11-6377-00 Before using this information, be
More informationAutomatic Fire Alarm Service Provider Computer Interface Specification for Extended Alarm Protocol (XAP) Devices
March 2014 Version 1.5 Automatic Fire Alarm Service Provider Computer Interface Specification for Extended Alarm Protocol (XAP) Devices For the New Zealand Fire Service December 2013 Copyright New Zealand
More informationXML: extensible Markup Language. Anabel Fraga
XML: extensible Markup Language Anabel Fraga Table of Contents Historic Introduction XML vs. HTML XML Characteristics HTML Document XML Document XML General Rules Well Formed and Valid Documents Elements
More informationDraft Response for delivering DITA.xml.org DITAweb. Written by Mark Poston, Senior Technical Consultant, Mekon Ltd.
Draft Response for delivering DITA.xml.org DITAweb Written by Mark Poston, Senior Technical Consultant, Mekon Ltd. Contents Contents... 2 Background... 4 Introduction... 4 Mekon DITAweb... 5 Overview of
More informationGetting a Handle on Release Management with DITA Fred Lass Senior Solutions Architect Astoria Software Managing Multiple Releases Software control systems maintain i multiple l releases of their product
More informationETSI TS 184 009 V2.0.0 (2008-06) Technical Specification
TS 184 009 V2.0.0 (2008-06) Technical Specification Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Rules covering the use of TV URIs for the Identification
More informationWWW. World Wide Web Aka The Internet. dr. C. P. J. Koymans. Informatics Institute Universiteit van Amsterdam. November 30, 2007
WWW World Wide Web Aka The Internet dr. C. P. J. Koymans Informatics Institute Universiteit van Amsterdam November 30, 2007 dr. C. P. J. Koymans (UvA) WWW November 30, 2007 1 / 36 WWW history (1) 1968
More informationIHE Pharmacy Technical Framework Supplement. Pharmacy Medication List (PML) Trial Implementation
Integrating the Healthcare Enterprise 5 IHE Pharmacy Technical Framework Supplement 10 Pharmacy Medication List (PML) 15 Trial Implementation 20 Date: September 29, 2014 Author: IHE Pharmacy Technical
More informationXml Mediator and Data Management
Adaptive Data Mediation over XML Data Hui Lin, Tore Risch, Timour Katchaounov Hui.Lin, Tore.Risch, Timour.Katchaounov@dis.uu.se Uppsala Database Laboratory, Uppsala University, Sweden To be published in
More informationIBM Unica emessage Version 8 Release 5 February 19, 2014. Transactional Email Administration Guide
IBM Unica emessage Version 8 Release 5 February 19, 2014 Transactional Email Administration Guide Note Before using this information and the product it supports, read the information in Notices on page
More informationBusiness Object Document (BOD) Message Architecture for OAGIS Release 9.+
Business Object Document (BOD) Message Architecture for OAGIS Release 9.+ an OAGi White Paper Document #20110408V1.0 Open standards that open markets TM Open Applications Group, Incorporated OAGi A consortium
More informationAuthentication Context Classes for Levels of Assurance for the Swedish eid Framework
Authentication Context Classes for Levels of Assurance for the Swedish eid Framework Version 1.0 2013-07-01 1 (5) 1 INTRODUCTION 3 2 DEFINED AUTHENTICATION CONTEXT CLASSES 3 2.1 LEVEL OF ASSURANCE LEVEL
More informationIHE IT Infrastructure Technical Framework Supplement. Secure Retrieve (SeR) Trial Implementation
Integrating the Healthcare Enterprise 5 IHE IT Infrastructure Technical Framework Supplement 10 Secure Retrieve (SeR) 15 Trial Implementation 20 Date: August 31, 2015 Author: IHE ITI Technical Committee
More informationCite My Data M2M Service Technical Description
Cite My Data M2M Service Technical Description 1 Introduction... 2 2 How Does it Work?... 2 2.1 Integration with the Global DOI System... 2 2.2 Minting DOIs... 2 2.3 DOI Resolution... 3 3 Cite My Data
More informationDesign Grammars for High-performance Speech Recognition
Design Grammars for High-performance Speech Recognition Copyright 2011 Chant Inc. All rights reserved. Chant, SpeechKit, Getting the World Talking with Technology, talking man, and headset are trademarks
More informationWorking with the Cognos BI Server Using the Greenplum Database
White Paper Working with the Cognos BI Server Using the Greenplum Database Interoperability and Connectivity Configuration for AIX Users Abstract This white paper explains how the Cognos BI Server running
More informationCombining SAWSDL, OWL DL and UDDI for Semantically Enhanced Web Service Discovery
Combining SAWSDL, OWL DL and UDDI for Semantically Enhanced Web Service Discovery Dimitrios Kourtesis, Iraklis Paraskakis SEERC South East European Research Centre, Greece Research centre of the University
More information[MS-ASMS]: Exchange ActiveSync: Short Message Service (SMS) Protocol
[MS-ASMS]: Exchange ActiveSync: Short Message Service (SMS) Protocol Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications
More informationUsing XML to Test Web Software Services. Modern Web Sites
Using XML to Test Web Software Services Jeff Offutt Information & Software Engineering George Mason University Fairfax, VA USA www.ise.gmu.edu/faculty/ofut/ Joint research with Suet Chun Lee, GMU PhD student
More informationIBM SPSS Collaboration and Deployment Services Version 6 Release 0. Single Sign-On Services Developer's Guide
IBM SPSS Collaboration and Deployment Services Version 6 Release 0 Single Sign-On Services Developer's Guide Note Before using this information and the product it supports, read the information in Notices
More informationE-mail Listeners. E-mail Formats. Free Form. Formatted
E-mail Listeners 6 E-mail Formats You use the E-mail Listeners application to receive and process Service Requests and other types of tickets through e-mail in the form of e-mail messages. Using E- mail
More informationStreamLink 5.0. StreamLink Configuration XML Reference. November 2009 C O N F I D E N T I A L
StreamLink Configuration XML Reference November 2009 C O N F I D E N T I A L Contents Contents 1 Preface... 1 1.1 1.2 1.3 1.4 1.5 1.6 What... this document contains 1 About... Caplin document formats 1
More informationPHIN DIRECTORY EXCHANGE IMPLEMENTATION GUIDE. Version 1.0
PHIN DIRECTORY EXCHANGE IMPLEMENTATION GUIDE Version 1.0 May 16, 2007 VERSION HISTORY Version # Implemented By Revision Date Approved By Approval Date Reason 0.1 Robb Chapman 02/25/2006 Initial Draft 0.2
More informationNEMA Standards Publication PS 3 Supplement 41. Digital Imaging and Communications in Medicine (DICOM) Digital Signatures
NEMA Standards Publication PS 3 Supplement 1 Digital Imaging and Communications in Medicine (DICOM) Digital Signatures Status: Final Text Sep 001 Prepared by DICOM Standards Committee, Working Group 1
More informationGuide to SQL Programming: SQL:1999 and Oracle Rdb V7.1
Guide to SQL Programming: SQL:1999 and Oracle Rdb V7.1 A feature of Oracle Rdb By Ian Smith Oracle Rdb Relational Technology Group Oracle Corporation 1 Oracle Rdb Journal SQL:1999 and Oracle Rdb V7.1 The
More informationXML Processing and Web Services. Chapter 17
XML Processing and Web Services Chapter 17 Textbook to be published by Pearson Ed 2015 in early Pearson 2014 Fundamentals of http://www.funwebdev.com Web Development Objectives 1 XML Overview 2 XML Processing
More information[MS-WSSDM]: Windows SharePoint Services: Content Database Data Migration Communications Protocol Specification
[MS-WSSDM]: Windows SharePoint Services: Content Database Data Migration Communications Protocol Specification Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation.
More informationChapter 2: Designing XML DTDs
2. Designing XML DTDs 2-1 Chapter 2: Designing XML DTDs References: Tim Bray, Jean Paoli, C.M. Sperberg-McQueen: Extensible Markup Language (XML) 1.0, 1998. [http://www.w3.org/tr/rec-xml] See also: [http://www.w3.org/xml].
More informationInterface Between Illinois Workforce Development System and Third-Party Services Tracking Systems
WIA Policy Letter No. 06-PL-24, Change 1 Attachment C Illinois Department of Commerce and Economic Opportunity Interface Between Illinois Workforce Development System and Third-Party Services Tracking
More information<Namespaces> Core XML Technologies. Why Namespaces? Namespaces - based on unique prefixes. Namespaces. </Person>
Core XML Technologies Namespaces Why Namespaces? bob roth 814.345.6789 Mariott If we combine these two documents
More informationCore Components Data Type Catalogue Version 3.1 17 October 2011
Core Components Data Type Catalogue Version 3.1 17 October 2011 Core Components Data Type Catalogue Version 3.1 Page 1 of 121 Abstract CCTS 3.0 defines the rules for developing Core Data Types and Business
More informationTECHNICAL REPORT onem2m; Application Developer Guide (onem2m TR-0025 version 1.0.0 Release 1)
TR 118 525 V1.0.0 (2016-03) TECHNICAL REPORT onem2m; Application Developer Guide (onem2m TR-0025 version 1.0.0 Release 1) 2 TR 118 525 V1.0.0 (2016-03) Reference DTR/oneM2M-000025 Keywords application,
More informationby LindaMay Patterson PartnerWorld for Developers, AS/400 January 2000
Home Products Consulting Industries News About IBM by LindaMay Patterson PartnerWorld for Developers, AS/400 January 2000 Copyright IBM Corporation, 1999. All Rights Reserved. All trademarks or registered
More informationAn Oracle White Paper October 2013. Oracle Data Integrator 12c New Features Overview
An Oracle White Paper October 2013 Oracle Data Integrator 12c Disclaimer This document is for informational purposes. It is not a commitment to deliver any material, code, or functionality, and should
More informationGlossary of Object Oriented Terms
Appendix E Glossary of Object Oriented Terms abstract class: A class primarily intended to define an instance, but can not be instantiated without additional methods. abstract data type: An abstraction
More information[MS-SPACSOM]: Intellectual Property Rights Notice for Open Specifications Documentation
[MS-SPACSOM]: Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages,
More informationSoftware Requirement Specification Web Services Security
Software Requirement Specification Web Services Security Federation Manager 7.5 Version 0.3 (Draft) Please send comments to: dev@opensso.dev.java.net This document is subject to the following license:
More informationBusiness Process Management with @enterprise
Business Process Management with @enterprise March 2014 Groiss Informatics GmbH 1 Introduction Process orientation enables modern organizations to focus on the valueadding core processes and increase
More informationOpen Source VoiceXML Interpreter over Asterisk for Use in IVR Applications
Open Source VoiceXML Interpreter over Asterisk for Use in IVR Applications Lerato Lerato, Maletšabisa Molapo and Lehlohonolo Khoase Dept. of Maths and Computer Science, National University of Lesotho Roma
More informationAn XML Based Data Exchange Model for Power System Studies
ARI The Bulletin of the Istanbul Technical University VOLUME 54, NUMBER 2 Communicated by Sondan Durukanoğlu Feyiz An XML Based Data Exchange Model for Power System Studies Hasan Dağ Department of Electrical
More informationEnterprise Content Management (ECM) Strategy
Enterprise Content Management (ECM) Strategy Structured Authoring August 11, 2004 What is Structured Authoring? Structured Authoring is the process of creating content that is machine parsable. -2- What
More informationOpenEmbeDD basic demo
OpenEmbeDD basic demo A demonstration of the OpenEmbeDD platform metamodeling chain tool. Fabien Fillion fabien.fillion@irisa.fr Vincent Mahe vincent.mahe@irisa.fr Copyright 2007 OpenEmbeDD project (openembedd.org)
More information