[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fw: Submission of OASIS DITA 1.1 CS for approval
Hi, all. This submission note got to Mary McRae on time week before last, but did not make it into these email archives due to coming from a non-member email account. The submission is okay. I just wanted to get the text into the record here, as the links represent the lastest referenced material for the approval. Upon approval, dates may be changed, nothing more. Regards, -- Don Day Chair, OASIS DITA Technical Committee IBM Lead DITA Architect Email: firstname.lastname@example.org 11501 Burnet Rd. MS9033E015, Austin TX 78758 Phone: +1 512-838-8550 T/L: 678-8550 "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot ----- Forwarded by Don Day/Austin/IBM on 06/25/2007 12:12 PM ----- "donday" <email@example.com> Sent by: To firstname.lastname@example.org email@example.com cc firstname.lastname@example.org 06/13/2007 10:29 Subject PM Submission of OASIS DITA 1.1 CS for approval Please respond to email@example.com The OASIS DITA Technical Committee hereby submits the DITA 1.1 Committee Specification for consideration as an OASIS Standard. (a) Links to the approved Committee Specification in the TC's document repository, and any appropriate supplemental documentation for the specification: Overview doc: http://www.oasis-open.org/committees/download.php/24316/overview-html.zip Architectural specification: http://www.oasis-open.org/committees/download.php/24314/archspec-html.zip http://www.oasis-open.org/committees/download.php/24315/archspec.pdf Language specification: http://www.oasis-open.org/committees/download.php/24318/langspec-html.zip http://www.oasis-open.org/committees/download.php/24319/ditaref-type.pdf (b) The editable version of all files that are part of the Committee Specification: Overview doc: http://www.oasis-open.org/committees/download.php/24316/overview-html.zip Architectural specification: http://www.oasis-open.org/committees/download.php/24313/archspec.zip Language specification: http://www.oasis-open.org/committees/download.php/24317/langspec.zip DTDs: http://docs.oasis-open.org/dita/v1.1/CD02/dtd/ditadtd.zip Schemas: http://docs.oasis-open.org/dita/v1.1/CD02/schema/ditaschema.zip (c) Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or reference, including fragments of such, are well formed, and that all expressions are valid: The TC hereby certifies that all schema and XML instances are valid. (d) A clear English-language summary of the specification: The Darwin Information Typing Architecture (DITA) specification defines both a) a set of document types for authoring and organizing topic-oriented information; and b) a set of mechanisms for combining and extending document types using a process called specialization. The DITA 1.1 specification is designed to be backwards-compatible with 1.0-conforming applications. The following major changes to the architecture provide added functionality for 1.1: * A <bookmap> specialization for encoding book-specific information in a DITA map * A <glossentry> specialization for glossary entries * Indexing specializations for see, see-also, page ranges, and sort order * Improvements to graphic scaling capability * Improved short description flexibility through a new <abstract> element * Specialization support for new global attributes, such as conditional processing attributes * Support for integration of existing content structures through the <foreign> element * Support for new kinds of information and structures through the <data> and <unknown> elements * Formalization of conditional processing profiles (e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations; The work of the OASIS DocBook TC and the OASIS Open Document Format TC are related in the documentation realm to DITA, however the goals and design of DITA provide different capabilities for potentially wider user communities. To our knowledge, this specification has no relationship to any other work of other OASIS TCs or other standards developing organizations. (f) The Statements of Use presented above: The following statements of use have been provided to date by OASIS organization members: IBM: http://lists.oasis-open.org/archives/dita/200705/msg00017.html JustSystems (XMetaL): http://lists.oasis-open.org/archives/dita/200705/msg00015.html Flatirons Solutions: http://lists.oasis-open.org/archives/dita/200705/msg00012.html PTC-Arbortext: http://lists.oasis-open.org/archives/dita/200705/msg00010.html Comtech Services, Inc.: http://lists.oasis-open.org/archives/dita/200705/msg00024.html (g) The beginning and ending dates of the public review(s): Beginning 5 March 2007, ending 4 May 2007 A pointer to the announcement of the public review(s): http://lists.oasis-open.org/archives/tc-announce/200703/msg00007.html and a pointer to an account of each of the comments/issues raised during the public review period(s), along with its resolution: http://www.oasis-open.org/committees/download.php/24348/Public-comments.doc (h) An account of and results of the voting to approve the specification as a Committee Specification, including the date of the ballot and a pointer to the ballot: Request for CS approval ballot (9 May 2007): http://lists.oasis-open.org/archives/dita/200705/msg00025.html Announcement (24 May 2007): http://lists.oasis-open.org/archives/dita/200705/msg00054.html OASIS notification of approval: http://lists.oasis-open.org/archives/dita/200706/msg00000.html (i) An account of or pointer to votes and comments received in any earlier attempts to standardize substantially the same specification, together with the originating TC’s response to each comment; None on record. (j) A pointer to the publicly visible comments archive for the originating TC: http://lists.oasis-open.org/archives/dita-comment/ (k) A pointer to any minority reports submitted by one or more Members who did not vote in favor of approving the Committee Specification, which report may include statements regarding why the member voted against the specification or that the member believes that Substantive Changes were made which have not gone through public review; or certification by the Chair that no minority reports exist. None on record.