[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DITA Technical Committee Meeting Minutes: 11 December 2007
Hi all, 1. Please review the pending proposals for design-approved vote next week (copied into this email for your convenience) 2. The TC requested we reserve a 2-hour block for next week in case we need it to get through all the votes and all the open items that need to be closed next meeting. ------------- PENDING VOTES The following items will be voted upon at the next TC meeting: 1. #12007 - Indirect reference/keyref proposal http://www.oasis-open.org/committees/download.php/26365/IssueNumber1207v7a.html 2. #12031 - Discussion on Controlled values, #collection-type enumerations and glossaries http://www.oasis-open.org/committees/download.php/26359/IssueControlledValues12031.html 3. #12047 - add convenience elements for composing maps that set attribute defaults http://www.oasis-open.org/committees/download.php/26129/IssueMapConveniences12047.html 4. #12014 - Delayed conref resolution http://lists.oasis-open.org/archives/dita/200712/msg00003.html 5. #12015 - Conref Push http://lists.oasis-open.org/archives/dita/200712/msg00005.html 6. #12043 - allow draft-comment in more places http://www.oasis-open.org/committees/download.php/26378/IssueNumber12043.html 7. #12050a - longdescref, scope, etc http://www.oasis-open.org/committees/download.php/26373/IssueNumber12050a.html 8. #12060 - verbatim inclusion of text http://www.oasis-open.org/committees/download.php/26374/IssueNumber12060.html ------------- Gershon L Joseph Director of Technology and Single Sourcing Tech-Tav Documentation Ltd. Secretary, OASIS DITA Technical Committee Secretary, OASIS DITA Translation Subcommittee Member, OASIS DocBook Technical Committee +972-8-974-1569 (direct) +972-57-314-1170 (mobile) http://www.tech-tav.com
DITA Technical Committee Meeting Minutes: 11 December 2007
Chaired by Don Day <dond@us.ibm.com>
Minutes by Gershon Joseph <gershon@tech-tav.com>
-------------
PENDING VOTES
The following items will be voted upon at the next TC meeting:
1. #12007 - Indirect reference/keyref proposal
http://www.oasis-open.org/committees/download.php/26365/IssueNumber1207v7a.html
2. #12031 - Discussion on Controlled values, #collection-type enumerations and glossaries
http://www.oasis-open.org/committees/download.php/26359/IssueControlledValues12031.html
3. #12047 - add convenience elements for composing maps that set attribute defaults
http://www.oasis-open.org/committees/download.php/26129/IssueMapConveniences12047.html
4. #12014 - Delayed conref resolution
http://lists.oasis-open.org/archives/dita/200712/msg00003.html
5. #12015 - Conref Push
http://lists.oasis-open.org/archives/dita/200712/msg00005.html
6. #12043 - allow draft-comment in more places
http://www.oasis-open.org/committees/download.php/26378/IssueNumber12043.html
7. #12050a - longdescref, scope, etc
http://www.oasis-open.org/committees/download.php/26373/IssueNumber12050a.html
8. #12060 - verbatim inclusion of text
http://www.oasis-open.org/committees/download.php/26374/IssueNumber12060.html
-------------
The DITA Technical Committee met on Tuesday, 11 December 2007 at 08:00am PT for
120 minutes.
1. Roll call
We have quorum.
2. Approve minutes from previous business meeting:
* http://lists.oasis-open.org/archives/dita/200712/msg00009.html (4 Dec 2007)
Accepted by acclamation.
3. Business:
1. ITEM: Proposals for Design Approval vote:
1. None
2. ITEM: Review prepared proposals:
1. Check status of ITEM: #12011 - Generic Task Type (Houser)
* http://lists.oasis-open.org/archives/dita/200711/msg00005.html
* http://lists.oasis-open.org/archives/dita/200711/msg00046.html (Houser follow up)
Alan sent the revised content models to the list shortly before the
TC meeting started. Defer discussions to end of today's meeting.
[Gershon: Don, remember to add this item to next meeting's agenda]
2. ITEM: #12007 - Indirect reference/keyref proposal (Ogden et al.)
* http://www.oasis-open.org/committees/download.php/26365/IssueNumber1207v7a.html
Jeff: We posted the most recent draft of the proposal a few days ago.
The idea is to allow map authors to be able to override references
or text in topics. In order to use this feature, authors must have
set up their topics using key references. Map authors define keys
(or key names) and associate it to a resource...
Michael: It effectively lets you add an href almost everywhere, even
where the element does not have @href.
Jeff mentioned other use cases documented in the proposal. The most
common use case is to override content in topics.
DECISION: The TC accepted proposal #12007 for vote next meeting.
3. ITEM: #12031 - Discussion on Controlled values, #collection-type enumerations and glossaries
* http://www.oasis-open.org/committees/download.php/26359/IssueControlledValues12031.html
Don asked Erik whether we can consider this proposal now that the TC
has accepted the keyref proposal for vote.
Erik: I've changed the binding mechanism so that we can bind to
specific attributes and elements, instead of specific global
attributes. Also changed the declaration of the set of controlled
values to be a reference to a map instead of being defined in a
catalog. Other change was to add a labelling element subject to
a labeled groups of controlled values.
The purpose of the proposal is to define an enumeration of values
but scale up to taxonomy etc. for users who need that.
Erik clarified that this proposal has no dependency on the
enumerations proposal (#12022).
Erik suggested we vote on this one after the keyref proposal has been
voted in as design-approved.
The TC will consider this proposal for voting next week on condition
the keyref proposal is voted in next week; if keyref is not voted in
next week, this proposal will be dropped from DITA 1.2.
DECISION: The TC accepted proposal #12031 for vote next meeting,
provided the keyref proposal gets voted in.
4. ITEM #12047 - add convenience elements for composing maps that set attribute defaults (Hennum, Kimber, et al.)
* http://www.oasis-open.org/committees/download.php/26129/IssueMapConveniences12047.html
* http://lists.oasis-open.org/archives/dita/200711/msg00028.html (related update)
Erik: Basic notion is to add some conveniences for things you can do
with attributes within a map. Users are commonly aggregating maps, so
this part of the proposal is understood. The part that needs to be
understood is the notion of a topic set, which works as follows:
1) Define branch with topicset.
2) Then reuse with topicsetref (pull mode).
anchorref is push mode.
This is similar to map aggregation, but more fine-grained for
assembling maps.
DECISION: The TC accepted proposal #12047 for vote next meeting.
5. ITEM: #12014 - Delayed conref resolution (Priestley)
* http://lists.oasis-open.org/archives/dita/200712/msg00003.html
Michael: If you have a delivery format that allows for reuse of
fragments at display time, the way to communicate with that delivery
format will be resolved by user versus resolved by the display
architecture. Use case is Eclipse. Define sets of reuse
relationships that are resolved at display time instead of at
publishing/rendering time...
Clarification: For this release, the proposal applies to topics, not
to maps (since we didn't consider circular relations).
Discussion...
The TC accepted proposal #12014 for vote next meeting.
6. ITEM: #12015 - Conref Push (Priestley)
* http://lists.oasis-open.org/archives/dita/200712/msg00005.html
Michael: If you have a common component that is reused across multiple
deliverables and it has a common install path. Rather than having the
common install path list the installation steps for every single
component, if we let the other components say we're adding an install
step, then we push the common install step into the component. So
it's all managed by the other components, not the common component.
You don't need to rebuild the common component every time a new
component gets installed.
Technical requirements: New attribute with 4 values to determine how
we pull or push...
Discussion...
ACTION: Erik to change @mark to @push-mark.
The TC accepted proposal #12015 for vote next meeting, with changes
marked as ACTION.
7. ITEM: #12022 - make @role (and other enumerated attributes) unenumerated
* http://lists.oasis-open.org/archives/dita/200712/msg00023.html (kimber contributions)
* http://lists.oasis-open.org/archives/dita/200712/msg00028.html (ogden questions)
Erik summarized the rationale for the proposal: It boils down to a
decision on which attributes to open up and which ones should not be
opened up. Eliot's email lists the enumerations that should be
handled via controlled values and listed @collection-type as an
open issue.
Discussion...
Don: There is still room for a more refined proposal. Suggested Eliot
convenes an off-line meeting to resolve issues and home in on a
proposal.
Michael: It should not take much more discussion to close this off.
Suggested if we get a revised proposal towards the end of this week
we can still vote on it next week.
The idea is to reduce the impact, and still remove the enumerations
that probably should never have been in the spec in the first place.
ACTION: Eliot to have an offline meeting and drive to a revised
proposal by Friday. If that happens, we'll include this for vote
next meeting. if not we'll drop this proposal for 1.2.
8. ITEM: #12043 - allow draft-comment in more places
* http://www.oasis-open.org/committees/download.php/26378/IssueNumber12043.html (proposal)
* http://lists.oasis-open.org/archives/dita/200712/msg00026.html (ogden question)
Robert: Added <draft-comment> to <body>, <shortdesc> and <conbody>.
JoAnn: We feel it's important to have <draft-comment> in <title>
because there are often changes to titles.
Michael: If we do add it to <title>, would you expect it to show up
in the outputs?
JoAnn: No.
Paul suggested it's a style issue.
Others felt it's a DITA behavior definition and not a style issue.
Paul: Commenting on title is sort-of metadata. Perhaps that would be
a better approach in the future.
JoAnn: Usually draft comments indicate to authors what we expect
them to do.
The TC decided to keep Robert's proposal for DITA 1.2 scope and note
the need to consider <draft-comment> in <title> in DITA 1.3.
The TC accepted proposal #12043 for vote next meeting.
9. ITEM: #12050a - longdescref, scope, etc
* http://www.oasis-open.org/committees/download.php/26373/IssueNumber12050a.html (priestley)
Michael: This lets you reference a longdesc with more than just the
@href, but get the full set of attributes to get a real full
reference behavior. Similar model to xref, but it does not contain
text. It's more a "go to here to get text".
DECISION: The TC accepted proposal #12050a for vote next meeting.
10. ITEM: #12060 - verbatim inclusion of text
* http://www.oasis-open.org/committees/download.php/26374/IssueNumber12060.html (priestley)
* http://lists.oasis-open.org/archives/dita/200712/msg00024.html (kimber question)
Michael: Added a new element to the programming domain that lets you
populate <codeblock> with text from an external file. Modeled after
<xref>. Similar to <longdescref>.
DECISION: The TC accepted proposal #12060 for vote next meeting.
11. ITEM: #12038 - Acronym proposal
* http://www.oasis-open.org/committees/download.php/26361/IssueNumbe12038.html
* http://lists.oasis-open.org/archives/dita/200712/msg00015.html (grosso)
* http://lists.oasis-open.org/archives/dita/200712/msg00018.html (pickett)
* http://lists.oasis-open.org/archives/dita/200712/msg00022.html (hennum)
* http://lists.oasis-open.org/archives/dita/200712/msg00027.html (ogden)
JoAnn: The original purpose is a mechanism to deal with conref of
acronyms and their expansion forms. The Translation SC has worked
for 6 months to come up with an effective proposal. Concern is the
potential misuse of conrefs in translation of acronyms, which is
carefully described in the proposal...
Defining practice in both print and online output.
Introduced surface form to allow acronym lists that can be accessed
to build terminology database for translation.
Erik suggested merging this proposal with the glossary proposal.
Some discussion...
Robert: By using <term> with @keyref to glossentry we can use the
expansion defined in the proposal and authors don't need the conref.
Further discussion...
ACTION: Gershon to take the following discussions to the list:
* Need to expand how application identifies first occurrence of an
acronym?
* Check merging acronyms into glossary
* Check using keyref instead of conref
Running out of time. Michael suggested we pick up here next week and
vote on them the following week. The TC requested a 2-hour meeting
next week in case we need it. Gershon mentioned he probably won't
be able to make the second hour and we'll need a scribe to record
the second hour's minutes.
--Out of time. Meeting adjourned.--
12. ITEM: #12024 - Hazard Statement Domain
* http://www.oasis-open.org/committees/download.php/26390/IssueNumber12024.html
13. ITEM: #12040 - Machine Industry Task type
* http://www.oasis-open.org/committees/download.php/26165/IssueNumber12040.html
4. Ongoing: Review of "Items for discussion" list in the Frontage
* How much flexibility for specializers?
(per Gershon's suggestion, we'll discuss the 2-implementations rule next agenda)
4. Announcements/Opens
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]