dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Groups - DITA TC Meeting Minutes 01 July 2014 uploaded
- From: Nancy Harrison<nharrison@infobridge-solutions.com>
- To: dita@lists.oasis-open.org
- Date: Sat, 19 Jul 2014 10:15:46 -0700 (PDT)
Submitter's message
Minutes of the OASIS DITA TC
Tuesday, 1 July 2014
Recorded by N. Harrison
link to agenda for this meeting:
https://wiki.oasis-open.org/dita/PreviousAgendas
regrets: Robert Anderson (late), Bob Thomas, Joann Hackos
Standing Business
=================
Approve minutes from previous business meeting:
https://lists.oasis-open.org/archives/dita/201406/msg00046.html (24 June, Nancy Harrison)
Proposed by Kris, seconded by Dick, approved by TC
Subcommittee Reports
Help Subcommittee: ?
Announcements
none
Business
========
1. DITA 1.3 progress
- Redesign of "Contains and Contains by" (Anderson)
Robert; I think they're complete now; maybe a bit of tweaking, but they're done and checked in.
- First spec review (Eberlein & Anderson)
Kris; this has been on hold for about a month; the real issue is keys/key scopes; we're not yet clear how to deal with those; they require a bunch of work and reorg. Any volunteers
JimT; I'll help
Eliot; i should probably be involved.
- Transformation utilities and DITA 1.3 grammar files (Kimber)
Eliot; all of the tests against 1.2 XSDs pass, so they're valid and correct; still some issues with L&T DTDs, so I'm still working on those. We've talked about models that weren't inherently constrainable - for a content model to be constrained, it needs to be a repeating 'or' model -, but if setting up autoatic generation of an arbitrary constraint model for XSDs is possible, it's beyond me, so i'm going to provide XSDs that map as closely as possible to 1.2, plus the 1.3 functionality. I'm no longer trying to 'fix' the XSD design; it just may not be fixable. We provide XSDs that may or may not be programmatically constrainable for all constraints. I've set up the base vocabulary models as needed to be constrainable.
Kris; what do we want to do?
Eliot; wnyone have strong feelings about this?
Don; on issue; can we train community that XSDs are incapable of supporting complete DiTA architecture? should they be used only for authoring?
Eliot; but you'd still have to modify the XSD files as supplied by OASIS.
Don; but people don't use schemas very much, because they're not very useful.
Eliot; Serna and XOpus only used XSDs, Serna is no longer in use, I don't know about XOpus.
Don; both editors are stil viable, not leaders, but still viable
Eliot; most editors use DTDs only, that's why no one's reporting problems
Don; people can be using XSDs derived from drds.
Don; should we just tell community that XSDs are 'bad boys'?
Eliot it's not that; the reality is that because of the way XSD spec is written, it's almost impossible to use its 'redefine' facility to do constraints, So we have to manually rewrite XSDs, it may not always be possible, and we're not going to do it for 1.3.
BobT; why supply XSDs at all?
Eliot; we've done it from the beginning, then it looked like XSDs would be the primary schema, but it never happened.
Don; we could say that while we support them, since we went to RNG, it doesn't look like we can support the design pattern with the XSD schemas.
Eliot; it's not that they can't support it, but it requires a case-by-case recrafting of each schema. e.g. task content. There doesn't seem to be a programmatic way to apply contraints to XSD models; Generating working XSD from DTDs or RNG simply isn't possible without hand-crafting.
Kris; so what is our position viv a vis this?
Robert; We don't have a position; IBM never used XSDs
Eliot; i'll draft a position paper on this. also BobT did some work and discovered an implementation issue
2. Report from Congility 2014 (Priestley)
[held tillMichael on call]
3. Continuing item: Questions about OASIS document-type shells for DITA 1.3
https://lists.oasis-open.org/archives/dita/201406/msg00019.html (Anderson, 10 June 2014)
Kris; we had some discussion, decided we needed a spreadsheet to explain these. I thought we had one in the spec, but we don't.
Eliot; i did find places where things didn't line up, and fixed them for 1.2, to make sure that what I'm generating actually matched 1.2, So we're now in a position to take direction on what shells should actually be for 1.3
Robert; in order to get that, we need the spreadsheet, to know what domains are available for which shells.
Kris; info may be spread around in spec for 1.2
Eliot; one advantage of RNG is that this stuff is very clear in RNG files; I think the only shells in questions are ditabase, bookmap, and the tech content map,
Kris; Robert had questions about bookmap; we think what we had for classification map for 1.2 wasn't in line with the tech. content map, and we wanted to change that.
Eliot; I think it's better to have more domains included rather than less.
Kris; I just want it to be organized and decided on
AI; Robert will look for the topics and put it together
Eliot; I can put together a spreadsheet on what I have for 1.2
4. On-going item: DITA 1.3 webinar, jointly sponsored by DITA TC and DITA Adoption TC -- Thursday, 31 July 2014
[discussion of date change; OASIS has conflicts around original date, and we need to have a date not only for the weinar, but for a rehearsal a day or two before. Will either be the 29/30 or the following week.]
Kris; one idea was to start with a poll; maybe 'are you using keys', any others? any other thoughts?
Current Webinar Program:
Introduction ? JoAnn Hackos
Update on the DITA 1.3 status ? Kris Eberlein
Troubleshooting ? Bob Thomas
Release Management ? Tom Cihak
Scoped Keys ? Chris Nitchie
Branching ? Robert Anderson
Relax NG ? Eliot Kimber
Learning and Training ? Mark Meyers
DITA Help ? Tony Self or Stan Doherty
DITA Domains ? Nancy Harrison
Q&A
closed at 11:55
-- Nancy Harrison
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]