Ranking

Issue #

Issue Title

Description of proposal

Owner

1

1
Major

Keyword (semantic)

Elaborate on the semantic role of keyword (issue of multiple meanings on this single name)

JoAnn Hackos, Paul Prescod

`

2

Keyword (nesting)

Extend by allowing keyword to nest (more conref and specialization options). This is related to number 1

JoAnn Hackos, Paul Prescod

`

3

skipped record?

`

4
Major

Use subset of OASIS xNAL standard for addresses

New language addition for address metadata (or extend via specialization). Related to bookmap.

Chris Kravogel, Nancy Harrison

2

5

Add ANSI warning labels as addition to the <note> element

Extend the existing enumerated @type for note for additional values. (or create a domain for the purpose)

Chris Kravogel, Bruce Esrig, JoAnn Hackos

`

6

Make @role (and other enumerated attributes) un-enumerated.

The issue is that the role="other" plus otherrole approach is only semi-extensible

Michael Priestley will write something up

2

7

Reconcile metadata elements in topics versus maps

In map.dtd, these elements have specific content restrictions that are not true in topics: shortdesc, searchtitle, linktext. Related to #12.

Yas Etessam

`

8

Allow <tm> to contain images or logoized content

Issue: tm content should be processible; is image consistent with this design principle? Is there a best practice instead for trademarked logo images or glyphs?

Chris Kravogel, Rob Frankland

`

9

Add new DATA element for extensible metadata and hybrid documents (was: Specialize new DATA element from keyword)

Design change intended to enable core semantic identification of a structure that can be specialized in many ways for data structures.

Eric Sirois, Erik Hennum

`

10 (see next)

Navtitle as element

For parallelism with the topic metadata (prototitle attribute)

Robert Anderson

2

11

Create elements for text attributes with translatable text

For the sake of translatability and reusability (neither easy to do with attribute content)

Robert Anderson

2

12

Consider making most universal attributes completely universal

Consistency issues, ease of maintenance (related to #7):
Add metadata attributes to table rows
Add @id and @conref to all
Add @outputclass to linkinfo, linktext

Robert Anderson

3

13 related to 17
Major

Create containers for steps and other elements

Enable specifying a range of peer targets

Michael Priestley, Alan Houser

1

14
Major

Specialize glossary entry and definition elements

Forum requests

Michael Priestley, Chris Kravogel, Bruce Esrig; some IBM folks have strong interest here

`

15
Major

Allow role names to be namespaced

Processing consideration

Paul Prescod

1

16
Major

Extend the link syntax to allow for indication of the use context for a link target

To clarify problems related to links and re-use

None yet

2

17
Major

Conref improvements

Per deepdive #5:
Better judging of domain matching
Metadata reuse across topics and maps
Generalization on the fly

Michael Priestley

`

18

Move @format and @scope into rel-atts

Consistency for linking models

Robert Anderson

2

19
Major

Introduce new, more general task type (between topic and task)

Popular request

Bruce Esrig, Robert Anderson, Indi Liepa?

6

20
Major

Extensible metadata attributes

Design improvement to extend DITA attribute set; tactical methods needed for now

Michael Priestley

items 21-30 were skipped in a previous renumbering--nothing is missing here

`

31
Major

Side-by-side implementation of DITA ids and xml:id

Resolve differences between standard W3C methods and DITA's current processing-enforced model.

Yas Etessam

`

32 (is pre req for 33)Major

Integration of domain elements with structural elements of the topic

The most general strategy would be to try to decouple the packaging of modules from the element inheritance hierarchy...

Erik Hennum

`

33 depends on 32

Move <refsyn> to a domain (e.g. Programming or Software Domain)

(dependent on outcome of 32)

None yet

1

34
Major

Replacement domain

Currently, the logic of domain specialization means that an element specialized in a domain cannot be prevented from appearing in a DTD everywhere where the ancestor/inherited element can occur. Domain specialisation is powerful, but it would be more useful in practice with an exclusion capability, so that not all the elements would automatically be inherited in all valid locations.

Erik Hennum, Chris Kravogel, Michael Priestley (all "interested"; no real owner yet)

`

35
Major

Support foreign content vocabularies such as MathML and SVG

The specific proposal is to introduce a DITA <unknown> element with a content model that allows any content.

Eric Sirois

1

36

Extensible metadata by expressing data in map structures


The specific proposal is to add a value attribute to the topicref element so it can be specialized and nested to represent metadata.

Erik Hennum

2 +

37
Major

Reconciling topic <link> and map <topicref> elements

In DITA 1.0, a topic expresses a link with a different element than a map. As a result, authors can't copy and paste between topics and maps, etc..

The specific proposal is to allow a <topicref> element in the <related-links> element.

Note: Appears to be high risk/high cost wrt transforms!

Erik Hennum

4 ++

38
Major

Bookmap / bkinfo revision

Validate the existing markup and make it formal ASAP to support FO activity in user community!
Note: Judged High Priority by the TC.

Chris Kravogel, Nancy Harrison, JoAnn Hackos

1

39
Major

Policy-based style mechanism


If DITA 1.1 provides better support for books (for instance, through a bookmap specialization), it will become important to specify styling for the book.

JoAnn Hackos

1

40
Major

Keyref architecture

The keyref attribute is intended to provide a key-based referencing scheme, with a level of indirection to allow for remapping of targets when content is reused in contexts where the target is unavailable. Note: Judged by TC to be a complex issue.

Michael Priestley, Rob Frankland, Bruce Esrig

1

41 (see 42)


Allow expanding the shortdesc model.


Sometimes the existing content model is insufficient; there are times when the opening paragraph needs to contain a list for example.

Note: Has processing implications.

Michael Priestley

1

42 (see 41)

Allow contracting the shortdesc model.

Conversely, there are times when the opening paragraph of content is already too long for use as hoverhelp/link previews.

Consider providing a marker element within shortdesc to allow authors to define a particular sentence within the shortdesc for use in hoverhelp, without affecting the shortdesc's function as first paragraph of content in other contexts.

Michael Priestley

`

43
Major

Semantic (implicit) linking

There are cases where semantic, phrase-level markup in DITA content has clear equivalents in topic-level markup.Note: Judged by the TC to be a higher priority.

Michael Priestley, Bruce Esrig, Alan Houser

`

44

Keep indextermref (or redefine its function)

Currently deprecated

None yet

2 +

45

Specialize See, See Also indexing elements.

Popular request

Bruce Esrig, Robert Anderson, Chris Wong

3

46 (related to "new task")
Major

Allow substeps to be used as steps elsewhere

Popular request

JoAnn Hackos

1

47
Major

Structured section

Issue is that section at the general level cannot constrain number and placement of titles; Constrain the core def? Specialize for structure?

Yas Ettesam

2

48
Major

Support change history and annotations in prolog

New prolog elements or specializations. This is related to bookmap.

Chris Kravogel, Nancy Harrison

'

49

It would be good if the actual markup elements (eg HTML/XHTML/XSL-FO elements) produced by the DITA stylesheets could be separated from the XSLT logic a bit more.

write-in by Anton Douche'

This could be somewhat related to issue 39, but I couldn't quite be sure.

We would like to customise the output markup, but the XSLT processing logic can be quite involved and editing them directly puts you at a disadvantage when it's time to merge in upgrades to the stylesheets when a new DITA toolkit is released.

One related process that could possibly be used to base this separation on is the localisation of strings. Of course localising strings seems much easier than localising the output markup.

Processing request for DITA OpenToolkit, but not part of the spec. Should be removed from this list.

None yet

"Off the list" approved items added in:

Ranking

Issue #

Issue Title

Description of proposal

Owner

List_of_DITA_1.1_Work_Items (last edited 2009-08-12 18:02:45 by localhost)