"fell off the list" items--review to ensure 1.1 scope completeness

[Don Day <dond@us.ibm.com>]

The items left behind by not being explicitly designated for the 1.1 cutoff
include:
   #7 reconcile metadata elements in topics versus maps
   #13 Create containers for steps and other elements
   #46 Allow substeps to be used as steps elsewhere
   #1 Keyword (semantic role of keyword)
   #16 Extend link syntax to allow indicating context of a target
   #36 Extensible metadata by expressing data in map structures
   #39 Policy based style
   #41 Allow expanding the shortdesc model (related to #42, which IS on the
   list)
   #48 Support change history and annotations in prolog
   #10 Navtitle as element (subsumed into #11?)
   #15 Allow role names to be namespaced
   #18 move @format and @scope into rel-atts
   #31 Side-by-side implementation of DITA ids and xml:id
   #33 Move <refsyn> to a domain (depends on #32, which was accepted)
   #44 Keep indextermref (or redefine its function)
   #49 Better separation of XSL-FO names from XSLT logic (looks like
   Toolkit req)


Unnumbered contributions that arrived SINCE the original list was gathered
and weighted:


   Spec and process issues (from Yas's notes, other comments):
   Update DITA 1.0 DTD/Schema specification (bug fixes and comment edits)
   http://lists.oasis-open.org/archives/dita/200507/msg00058.html among
   others

   OASIS artifact naming guidelines (to follow where applicable)
   http://lists.oasis-open.org/archives/dita/200507/maillist.html

   Documenting DITA design principles (not approved yet)
   http://lists.oasis-open.org/archives/dita/200510/msg00005.html

   Details in the DITA spec--Priestley ("There are some cases... where the
   spec needs to be updated")
   http://lists.oasis-open.org/archives/dita/200510/msg00059.html
   - behavior of conref with attributes on the referencing element
   - why a content fragment has to be addressed within a topic

   Styling options for conditional text

   Recognizing DITA documents

New worked proposals (unnumbered) from members:

   Extensibility of DITA through new attributes
   http://lists.oasis-open.org/archives/dita/200508/msg00065.html
   http://lists.oasis-open.org/archives/dita/200508/msg00069.html and
   following

   Styling Options for Conditional Text
   http://lists.oasis-open.org/archives/dita/200508/msg00066.html and
   following
   http://lists.oasis-open.org/archives/dita/200509/msg00025.html

   Recognizing DITA Documents
   http://lists.oasis-open.org/archives/dita/200508/msg00067.html and
   following

   Start of documenting DITA design principles (Paul Prescod)
   http://lists.oasis-open.org/archives/dita/200510/msg00005.html

   Module Registry proposal (Bruce Esrig)
   http://lists.oasis-open.org/archives/dita/200510/msg00097.html

   Clarification of Chunk attribute (Erik Hennum)
   http://lists.oasis-open.org/archives/dita/200511/msg00070.html

   Criteria for making distinction between general and industry-specific
   DTDs/schemas (future agenda discussion)



Regards,
--
Don Day
Chair, OASIS DITA Technical Committee
IBM Lead DITA Architect
Email: dond@us.ibm.com
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