OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Groups - DITA TC Meeting Minutes 3 Dec 2013 uploaded


Submitter's message
Action Items:
1. Kris offered to contact the presenting group for DITA-S1000D webinar, and see if they can record it.
2. proposal reviews:
- Michael to have 13121 ready for discussion at 12/10 TC meeting
- Scott and Dick, and Robert if possible, to have reviews of 13112 ready by Friday, 10/6 to enable discussion on 12/10
- Eliot to complete review of 13106 in time for discussion on 12/10
3. Kris to set up a call with Robert, Chris, Eliot and herself to continue discussion of 13059a.
4. We need to capture the inconsistency (among @ names, beginning with ua-window vs. ux-window) added by proposals 13060/13061 as requiring a doc note in the spec;
5. Need attribute information for new topics introduced by proposal 13089: learningObjectMap and learningGroupMap (Myers)
6. Need feedback from Kimber and Helfinstine about new content concerning conrefs and ; introduced by 13001: Same topic URI reference syntax (Helfinstine)


=====================================================

Minutes of the OASIS DITA TC
Tuesday, 3 December 2013
Recorded by N. Harrison

regrets: Stan Doherty


Standing Business
=================
https://lists.oasis-open.org/archives/dita/201312/msg00010.html (26 November, Nancy Harrison)
Proposed by Kris, seconded by Joann, approved by TC


Subcommittee Reports
(TechComm SC: 3 December)
Joann reported that the SC is on vacation till next year; their current focus is on getting their 1.3 proposals through Stage 3 approval.

Announcements:
"S1000D-DITA bridge over troubled water" Webinar for December 10
https://lists.oasis-open.org/archives/dita/201312/msg00004.htmlnone
Kris; this is the French group that gave us the webinar; I think some TC members should attend
Chris noted that it's scheduled for 1 pm French time, so 4 am PT
Kris offered to contact the presenting group and see if they can record it...


Business
========
1. DITA 1.3 progress
Progress: 25 November - 1 December 2013: https://lists.oasis-open.org/archives/dita/201312/msg00002.html
Status of proposals in progress and in review: https://lists.oasis-open.org/archives/dita/201312/msg00013.html (updated, 3 December 2013)
Trello Board: https://trello.com/b/gPKH0OcF
Kris gave overview;
- 13121 MUST move into discussion by end of week; one required changed topic, coding requirements for XSDs, is not done.
- 13112. RelaxNG?, no reviews back from Robert or Scott, one back from George Bina, with some comments, won't change overall proposal but trying to come up with 2 complete reviews to move forward. Robert and Scott said they would complete their reviews this week. Eliot noted that he needed the reviews by Friday 12/6 in order to have it available by 12/10. Scott can do that; Robert wasn't sure.
Kris then asked if there was anyone on the TC with time, bandwidth, and expertise to review 13112? Dick said he'd take a look at it.
- 13106; Kris noted that Joann and Dawn have completed reviews, waiting on Eliot. Eliot said he could look at it today. Kris asked him to review it so the final proposal can be in KAVI for TC discussion by end of week.


2. DITA 1.3 proposals, stage 3

Questions:
13059a: Branch filtering
https://lists.oasis-open.org/archives/dita/201312/msg00009.html (Anderson, 2 December 2013)
Robert gave overview: based on Eliot's feedback, some changes are more substantial that others, e.g., the way you can have a branch of content filtered in a map that apply only to that branch of content.
1. renaming of files based on copy-to attribute; Eliot suggested replacing that with something that would give more control; use metadata @s rather than copy-to; makes it more logical to provide prefixes/suffixes for keyrefs. Does away with 1 new element and adds 6 new metadata elements.
2. stage 2 had a limitation on how you could express branches; Eliot disagreed, said if authors get into trouble, it's their fault; final proposal gets rid of that limitation; proposal will have to be updated to show how things will happen if you have conflicts at different branches. The reason for original limitation was to help iimplementors and to help authors.
Kris; Do you think potential functionality overrides issues with users getting into a mess?
Robert; Yes. And it's possible they might have been just as confused in the other situation as well. There are certainly valid reasons for doing so.
Eliot; I felt the limitations were also somewhat unenforcable.
Robert; Right, the only way is to have tools ignore nested filters
Kris; As a second reviewer on this proposal, I support these changes.
Also examples and processing order.
Robert, wrt examples; I put several in the proposal; some use generated HTML filenames; that is something that is true for my situation; Eliot disagrees and wants example filenames changes to show all the branch filter result maps
Eliot; We don't have to replace all examples
Robert; It's OK to include examples as long as they're understood to not be normative.
Kris; in the spec, all examples are by definition non-normative
Robert; Another item is related to processing order; Eliot laid out pretty strict processing order about how things would have to be done. I get really nervous about that. We've never done that since DITA 1.0, and different tools do different things in different orders.
Eliot; that is not true
Kris; we have never specified a set order in any DITA release
Eliot; thru 1.2, it's been clear that it cannot change the effective value of your content. The difference is: you'll get an error message because you have an unresolvable content reference. If not, I would not have voted for 1.2
Kris; any other TC members who would have strong opinions?
Chris; as a processor developer, the processor order reveals itself from the rules in the spec, even if the spec isn't explicit about them. With the rules for cascading, there is a definite order that is explicitly given in that part of the spec.
Eliot; The impostant thing is that the spec has to say what the right answer will be; that implies an order, We can give the right answer, and say 'in order to get that answer, you'd generally do that in that order.
Kris; we need to resolve this in another call; I'll set one up
ActionItem: Kris to set up a call with Robert, Chris, Eliot and herself to continue this discussion.

Ready for vote: Voting options are "Yes," "No," and "Abstain"

Proposal 13104, keyref on object (Kimber; Reviewers: Robert Anderson, Dick Hamilton)
Moved by Eliot, 2nded by Don, approved unanimously by TC
Yes votes: Anderson, Bissantz, Day, Eberlein, Hackos, Hamilton, Harrison, Helfinstine, Hudson, Kimber, Magliery, Myers, Nitchie

Proposal 13041: Facility for key-based, cross-deliverable referencing (Kimber; Reviewers: Jim Tivy, Chris Nitchie)
Moved by Eliot, 2nded by Joann, approved by TC
Yes votes: Anderson, Bissantz, Day, Eberlein, Hackos, Hamilton, Harrison, Helfinstine, Hudson, Kimber, Magliery, Myers, Nitchie

Ready for discussion:

Proposal 62: Table accessibility (Reviewers: Eliot Kimber, Don Day, Stan Doherty(?))
https://lists.oasis-open.org/archives/dita/201311/msg00149.html (DITA, uploaded 19 November)
https://lists.oasis-open.org/archives/dita/201311/msg00150.html (HTML, uploaded 19 November)
https://lists.oasis-open.org/archives/dita/201311/msg00151.html (PDF, uploaded 19 November)
Scott gave an overview; the proposal adds additional @'s to identify table headers and rows/columns for complex tables. The post-review version is basically unchanged technically from stage 2; the final proposal includes all docs and a complex table example; other examples which were originally in the proposal, but were detrmined to be superfluoous to the 1.3 spec, will be published as part of an Adoption TC article.
Resolution; this proposal will be voted on next week

Proposal 13060: Enhancement to (Help SC; Reviewers: Scott Hudson, Deb Bissantz, Robert Anderson)
https://lists.oasis-open.org/archives/dita/201311/msg00218.html (HTML, uploaded 25 November 2013; updated 26 November)
https://lists.oasis-open.org/archives/dita/201311/msg00217.html (DITA, uploaded 25 November 2013; updated 26 November)
Stan & Tony, the original proposer and the implementor, weren't on the call, so Robert (a reviewer) gave the overview. In stage 2, it was suggested that the proposal should make things more flexible by adding a 'data' subelement, which has been done. The proposal also adds 3 new @s on 'resourceid' to help identify help window information.
Eliot; We do have an inconsistency, with some @ names beginning with ua-window, and some with ux-window.
Joann; I think this is a necessary for relating help topics to software
ActionItem; we need to capture the inconsistency (among @ names) added by this proposal as requiring a doc note in the spec;
Resolution; this proposal will be voted on next week

Proposal 13056: Expand syntax for filtering attributes (Anderson; Reviewers: Deb Bissantz, Eliot Kimber)
https://lists.oasis-open.org/archives/dita/201311/msg00214.html (DITA, uploaded 26 November 2013)
https://lists.oasis-open.org/archives/dita/201311/msg00216.html (HTML, uploaded 26 November 2013)
https://lists.oasis-open.org/archives/dita/201311/msg00215.html (PDF, uploaded 26 November 2013)
Robert gave an overview; the problem was to expand those attributes even though the filtering @s can't be specialized. (not connected to discussion above)
Joann; Just to be clear, this only affects the filtering @s we've had in the past?
Robert; yes only product, platform, etc
Joann; we had discussed adding additional filtering @s; what happened?
Robert; This started as a proposal from Su-laine (adding @otherprops[1-5]); there was no one who wanted to champion that proposal. Eventually Robert made that into this one.
Joann; I thought this one was going to be implementing Su-laine's original proposal; we would like to be able to filter based on @s in prolog
Robert @s or elements?
Joann; elements.
Robert; there was no one willing to put the time into that.
Joann; well we need that...
Resolution; this proposal will be voted on next week


Proposal 13061: UA window definition (Help SC; Reviewers: Don Day, Robert Anderson)
https://lists.oasis-open.org/archives/dita/201311/msg00220.html (DITA, uploaded 26 November 2013)
https://lists.oasis-open.org/archives/dita/201311/msg00219.html (HTML, uploaded 26 November 2013)
Hold this till Help SC member present


3. New item: Missing (or extra) attribute on searchtitle
https://lists.oasis-open.org/archives/dita/201311/msg00228.html (Anderson, 27 November 2013)
https://lists.oasis-open.org/archives/dita/201311/msg00230.html (Day, 27 November 2013)


4. New item: Chunking and composite topics
https://lists.oasis-open.org/archives/dita/201312/msg00007.html (Nitchie, 2 December 2013)


5. DITA 1.3 infrastructure and editorial work
Redesign of attribute information in Language Reference topics reviewed by a small group (Hackos, Doherty, Harrison, Day)
Content for most approved proposals incorporated into topics in SVN
- Need attribute information for new topics introduced by proposal 13089: learningObjectMap and learningGroupMap (Myers)
- Need feedback from Kimber and Helfinstine about new content concerning conrefs and ; introduced by 13001: Same topic URI reference syntax (Helfinstine)
Kris reviewed above.


meeting closed at 12:00




-- Nancy Harrison
Document Name: DITA TC Meeting Minutes 3 Dec 2013

No description provided.
Download Latest Revision
Public Download Link

Submitter: Nancy Harrison
Group: OASIS Darwin Information Typing Architecture (DITA) TC
Folder: Meeting Notes
Date submitted: 2013-12-09 17:47:21



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]