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 16 July 2013 uploaded

Submitter's message
Minutes of the OASIS DITA TC
Tuesday, 16 July 2013
Recorded by N. Harrison

regrets: Kris Eberlein, Scott Hudson, Mark Myers

Standing Business
Minutes from last meeting:
https://www.oasis-open.org/apps/org/workgroup/dita/download.php/49963/minutes20130709.txt (9 July, Harrison, Hamilton, & Day)
These minutes weren't istrtibuted until just before this meeting, so members haven't yet had a chance to review them; they will be voted on next week

AMALGAMATED MINUTES (for ease of research):
Intro: https://lists.oasis-open.org/archives/dita/201307/msg00052.html
Aug-Dec 2011: https://www.oasis-open.org/committees/document.php?document_id=49821&wg_abbrev=dita
Jan-Dec 2012: https://www.oasis-open.org/committees/document.php?document_id=49822&wg_abbrev=dita
Jan-Jun 2013: https://www.oasis-open.org/committees/document.php?document_id=49823&wg_abbrev=dita

Subcommittee Reports:
None; TechComm SC for 6 Aug.


1. DITA 1.3 progress
Since Kris wan't on the call, Don asked ChrisN to report on the current status as recorded on the Trello board. Chris didn't think that there was anything significant to report.
Robert noted that he'd updated the board last week after the 9July meeting. Also, MichaelP still needs to remove #13108 from the board.

2. DITA 1.3 proposals, stage 2:

Note: We seem to have dealt with all of Eliot's proposals that were previously in the 'Holding area'

Ready for vote: Voting options are "Yes," "No," "No objections," "I don't understand the proposal," and "I have reservations"

Proposal 13104: Enable keyref for and (Kimber)
https://lists.oasis-open.org/archives/dita/201306/msg00074.html (DITA, uploaded 18 June)
https://lists.oasis-open.org/archives/dita/201306/msg00075.html (HTML, uploaded 18 June)
https://lists.oasis-open.org/archives/dita/201306/msg00076.html (PDF, uploaded 18 June)
Eliot moved the proposal, seconded by MikeB

Yes: Day, Anderson, Boses, Buchholz, Hackos, Hamilton, Harrison, Helfinstine, Kimber, Magliery, Nitchie, Priestley, Warman
NoObj. Bissantz

Proposal 62: Table accessibility (Hudson)
https://lists.oasis-open.org/archives/dita/201306/msg00130.html (DITA, uploaded 26 June)
https://lists.oasis-open.org/archives/dita/201306/msg00131.html (HTML, uploaded 26 June)
https://lists.oasis-open.org/archives/dita/201306/msg00129.html (PDF, uploaded 26 June)
Scott had sent regards, but recommended that we vote even if he wasn't present.
Since Scott wasn't on the call, Don moved the proposal, DickH seconded

Yes: Day, Bissantz, Boses, Buchholz, Hackos, Hamilton, Harrison, Helfinstine, Kimber, Nitchie, Priestley, Warman
NoObj. Anderson, Magliery

Ready for discussion:
Proposal 13105: Allow within lists (Kimber)
https://lists.oasis-open.org/archives/dita/201306/msg00067.html (DITA, uploaded 18 June)
https://lists.oasis-open.org/archives/dita/201306/msg00068.html (HTML, uploaded 18 June)
https://lists.oasis-open.org/archives/dita/201306/msg00069.html (PDF, uploaded 18 June)
- Don was going to provide an example
- Joann reiterated that techcomm SC is concerned about this; since most organizations will have to constrain it out.
- Eliot pointed out that since there's already a widely used constraint model for task - the strict task - it would be very straightforward to keep this out of strict asks and only add it to the 'general' task, a much looser model.
- MichaelP; Eliot, can you give me an example of why someone would want this
- Eliot; Basically, it's necesary for data conversion, to capture original data from a list, like original numbers or other attributes.
- MichaelP; So that could include mapping elements in a list back to requirements that required their creation?
- Joann; Using this, they might have something they had expected to be in output, and it wouldn't appear.
- MichaelP; But they already have it in various other places
- Joann; So what about the strict task?
- MichaelP; By using that constraint, you're reducing complexity, but also reducing consistency, since data is allowed everywhere else.
- Joann; I'll take this discission will take back to the TechComm SC.
- Don; One technical clarification; would constraints be for lists only?
- Eliot; The data element would only be allowed as the first child of steps, not between individual step elements.
Resolution: continued to next meeting

Proposal 13120: Vocabulary for publishing process details (Kimber)
https://lists.oasis-open.org/archives/dita/201306/msg00093.html (Kimber, implementation details not previously discussed)
https://lists.oasis-open.org/archives/dita/201306/msg00089.html (DITA, uploaded 20 June)
https://lists.oasis-open.org/archives/dita/201306/msg00090.html (HTML, uploaded 20 June)
https://lists.oasis-open.org/archives/dita/201306/msg00091.html (PDF, uploaded 20 June)
https://lists.oasis-open.org/archives/dita/201306/msg00092.html (Toolkit plugin, uploaded 20 June)
Eliot gave an overview;
To do cross-deliverable linking, the expectation is that there would need to be a 2-pass process. The output of the first pass is new set of key definitions, with real key locations for other publication, the 2nd pass gets the data located in the real keyref ocations.
2 parts to the proce4ss
1. generating intermediate keydefs
2. whoever is processing the intermediate keyset, has to know which keyset they're using, needs to know about all the various keysets, and what the particular target is, then they have to initiate processing for each root map
- Don; this is preserving the necessary info; how does the processor know when to create a new cache of the info?
- Eliot; There's no easy way to tell, you have to know what might have changed in your source, and that might change your output. so you can have a topic that contains all the publication specific info to process links across a doc set.
- Don; Are any other implementors looking at this problem? Who else besides Eliot are stakeholders?
- Eliot; This is a general problem for publishers, IBM has the requirement.
- Jim Tivy; I have some interest in this subject, a standard would be a good thing.
- Don; Is this related to cross-deliverable linking where the different documents are different types (e.g. linking from HTML to PDF docs or vice versa?
- JTivy; you need a key that represents the entire key space to guarantee that you can link as intended, so you need a correlation between authoring time keys and publishing time resources. How that happens is that the first pass generates a .ditamap with the correct key info, then the 2nd pass uses that info to create the final deliverables.
- Don; is there any author component to this, or is it all generated content?
- Eliot; Presumably it could be generated manually, but it wouldn't ordinarily be. The first pass is the record of the 'stateful' info.
- Don; I'd ask all TC members to please look at this, especially wrt its complexity, even though it's generally hidden from authors.

Resolution; continue discussion on this next week; need comments from either RAnderson or MPriestley

meeting closed at 11:59

-- Nancy Harrison
Document Name: DITA TC Meeting Minutes 16 July 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-07-22 23:25:32

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