1.2 Requirements Ranking

Top 5 critical:

12011 - I think the current task model is too specialized, precluding
many useful other specializations of task.

12016 - This is a key functionality that would help make the use of DITA
much easier and more natural

12047 - Maps are a key distinguisher for DITA and this proposal provides
needed and natural refinements

12007 - Need an indirection mechanism of some sort. Also need a "logical
name reference" mechanism. Keyref may or may not be one or the other of
these but it stands as a placeholder for the requirements.

12010 - This seems like an important refinement to the specialization
mechanism that needs to be done sooner rather than later.

Simple:

12001 - Implies no functional change to spec
12009 - Seems obvious and easy
12018 - Needed bug fix
12019 - Another non-controversial proposal
12022 - Obvious bug fix
12023 - Ditto
12024 - Easy
12028 - No functional change
12029 - Easy to implement, no functional change to existing docs
12035 - Requires a little design but should be non-controversial
12043 - Easy
12046 - Easy
12051 - Should be there already
12052 - Ditto

Issue that I didn't choose and why:

- 12008 - Potentially very complicated, not clear that it's needed,
could be controversial
- 12013 - Workaround exists to satisfy requirement
- 12015 - Potentially complicated, at least in terms of clearly defining
processing implications.
- 12020 - Can do this today with local specializations or just using