Regarding 13102, we still have a lot of work to do. After discussing with the SC, we uncovered a need for “inline” release notes, which caused us to go back
to the drawing board (as it were). The need is still there, and the concept is the same, but how it’s used and how it’s supported by markup are open questions.
-seth
From: dita-techcomm@lists.oasis-open.org [mailto:dita-techcomm@lists.oasis-open.org]
On Behalf Of JoAnn Hackos
Sent: Monday, February 25, 2013 8:09 AM
To: Kristen James Eberlein
Cc: dita-techcomm@lists.oasis-open.org
Subject: Re: [dita-techcomm] SC proposals for DITA 1.3
I expect Seth to conduct the SC vote on Bob's proposals next week. I'm one of the reviewers and I have completed my review. I have also nearly completed the topic for the arch spec and will also have that ready for review next week.
Again, please members, review Bob's proposals. You have plenty of time.
We are still waiting for Priestley on 13097. Seth needs for respond on 13102. I don't think there has been any progress.
We do need to ask the reviewers to complete their reviews, although I'm one of them and I've completed mine.
Sent from my iPad
710 Kipling Street Suite 400
Folks, I need you to assign deadlines for the following proposals. I understand that #13097 is dependent on #13121, for which Michael Priestley has given a deadline of March 15.
Does the subcommittee still intend on moving forward on #13102 for the DITA 1.3 release, or do you want to defer that to a future release of DITA?
|
Proposal #
|
Owner
|
Description
|
Stage
|
Comments
|
|
13086
|
TechComm SC
|
Add troubleshooting element to <step>
|
3
|
|
|
13096
|
TechComm SC
|
Add troubleshooting section to <task>
|
3
|
|
|
13097
|
TechComm SC
|
Troubleshooting topic
|
2
|
|
|
13098
|
TechComm SC
|
Add new troubleshooting value to @type attribute for <note>
|
3
|
|
|
13102
|
TechComm SC
|
Revision history/release management markup
|
2
|
|
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Co-chair, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
On 2/18/2013 12:19 PM, Kristen James Eberlein wrote:
OK, then a tentative deadline for when the DITA TC will see
proposals #13086, 13096, and 13098 would be helpful.
Here are some thoughts about the next moves that might be helpful in planning the deadline.
|
Item
|
Deadline
|
Comments
|
|
New topic for archSpec
|
Week of Feb 25-March 1
|
|
|
SC reviews stage-3 proposals
|
SC meeting on March 4? March 18?
|
|
|
Revisions to stage-3 proposals, based on feedback from SC
|
|
|
|
TC reviewers review stage-3 proposals
|
|
Allow a week or more for this
|
|
Revise stage-3 proposals based on feedback from reviewers
|
|
Allow a week or more for this
|
|
Stage-3 proposals submitted to TC
|
|
|
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Co-chair, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
On 2/18/2013 10:24 AM, JoAnn Hackos wrote:
GE 3 proposals of 13086 13096 13098 are ready except for the new topic for the arch spec explaining the relationships among the three options for troubleshooting. Our proposal for troubleshooting topic has been waiting for Michael Priestly's
proposal for the steps domain. He has made no progress on that as far as I know. Seth Park has made to progress that I know of on release management. I haven't checked on 13121 at this time to see what it is but just creating a steps domain will not complete
the troubleshooting topic proposal.
I hope to write the new topic the troubleshooting sometime in the next week. I just reviewed Bob's stage 3 proposals and feel they are complete.
Sent from my iPad
710 Kipling Street Suite 400
Dear members of the TechComm subcommittee:
I am contacting all individuals and subcommittees that have more than two proposals in the process for DITA 1.3. Below is a list of the proposals advanced by the subcommittee:
|
Proposal #
|
Owner
|
Description
|
Stage
|
Comments
|
|
|
|
13086
|
TechComm SC
|
Add troubleshooting element to <step>
|
3
|
|
|
|
|
13096
|
TechComm SC
|
Add troubleshooting section to <task>
|
3
|
|
|
|
|
13097
|
TechComm SC
|
Troubleshooting topic
|
2
|
|
|
|
|
13098
|
TechComm SC
|
New troubleshooting <note> type
|
3
|
|
|
|
|
13102
|
TechComm SC
|
Revision history/release management markup
|
2
|
|
|
|
|
13113
|
TechComm SC
|
Make <steps> available in troubleshooting topic
|
2
|
Hopefully handled by #13121
|
I'd like the SC to provide the following information:
-
Tentative date for when you think you will have the stage-3 proposals for proposals #13086, 13096, and 13098 ready.
-
Whether you plan to have the stage-3 proposals for #13086, 13096, and 13098 ready at the same time. Because of the questions previously posed by the TC and the content overlap, this might be a sensible approach.
-
An assessment of whether you think you will be advancing a stage-2 proposal for #13102.
I'm leaving #13097 out of this discussion, since it has a current dependency on proposal #13121. Ditto for #13113, which is really a placeholder for a less-favored implementation approach if #13121 does not materialize.
Best,
Kris
Kristen James Eberlein
Principal consultant, Eberlein Consulting
Co-chair, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
|