DITA Technical Committee Meeting Minutes 10 Nov 2009

["Gershon Joseph (gerjosep)" <gerjosep@cisco.com>]

 

 

Gershon Joseph Technical Leader, Engineering Product Development Services gerjosep@cisco.com Phone: +972 9 892-7157 Mobile: +972 57 314-1170	Cisco Systems, Inc. Israel Cisco home page

Think before you print.

This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.

Cisco Systems Limited (Company Number: 02558939), is registered in England and Wales with its registered office at 1 Callaghan Square, Cardiff, South Glamorgan CF10 5BT

 

DITA Technical Committee Meeting Minutes
========================================


The DITA Technical Committee met on 10 November 2009 at 08:00am PT for 60 
minutes.

Chaired by Don Day <dond@us.ibm.com>
Minutes recorded by Gershon Joseph <gerjosep@cisco.com>


Roll call
> Quorum was achieved.


Approve minutes from previous business meetings: 
* http://lists.oasis-open.org/archives/dita/200911/msg00024.html (3 November 2009, Joseph)
> Minutes approved by acclamation.


Subcommittee/liaison reports (as needed)

* OASIS DITA Help Subcommittee
> Stan: 3 updates:
> 1) We continue to work on a new DITA Help technologies guide. Challenges in 
>    trying to find a way to talk about all of the help-related tools in use 
>    today. How to be comprehensive and still objective is a challenge!
> 2) Collaboration / working with other committees touching on similar concerns
>    as we are, e.g. DITA for the Web SC. Going well. Also starting to reach 
>    out to the DITA in a Compound Environment SC. 
> 3) Defining and specifying features we believe as 1.3 candidates -- lang 
>    specializations. E.g. how do we code specific window types, window IDs, 
>    embedded UA, and others.

> Don asked Stan to solicit 1.2 statements of use from help SC members using 
> the new content.


Business:


ITEM: DITA 1.2 specification (revised by Eberlein 9 November 2009) 
* Spreadsheet and DITA topics located in the Subversion repository 
* Information about contributors, deadlines, editorial guidelines, Subversion 
  clients, and more 

* Business: 

  a. Progress report on spec review #2: All reviews will be completed by 13 
     November 

  b. Need to revise spec author/review schedule due to the following issues: 
     * Constraints proposals and issues 
     * Discussion around terminology 
     * Work being done to restructure conref/keyref/href material 
       The schedule below presupposes that the DITA TC resolve all open issues 
       during the November 10 and 17 meetings. If that does not happen, the 
       dates need to shift according to the delay
       1 December 2009 -- Third drafts complete; third internal review begins. 
                          This review will include the OASIS DITA Adoption 
                          Committee and the OASIS Technical Advisory Board. 
       22 December 2009 -- Third review complete; author begin working review 
                           comments.
       13 January 2009 -- Final draft ready to submit to OASIS for public 
                          review and official-approval process kick-off. This 
                          draft must include all substantive content; if we 
                          need to add substantive content after the public 
                          review begins, it will require us to restart the 
                          approval process.

  c. Need for authors to handle the following points (we might need to schedule
     an authors meeting) 
     * Implementing "referencing element" and "referenced element" terminology 
     * Implementing cascade vs. inherit terminology 
     * Moving content of some <draft-comment> elements -> XML comments; for the
       next review, we should be using <draft-comment> elements only for 
       comments to reviewers. 
     * Ensuring conformance statements are valid, correct and correctly marked 
       up ("must", "should" etc. correctly used and tagged) 

> Jeff clarified that everything would need to be ready for next review period,
> including DTDs and XSDs.

> Don: Need to consider that any new items coming up in the coming weeks are 
> going to be dealt with as errata or 1.3 items and won't be addressed as 1.2
> items.


ITEM: documentation of conref restrictions 
* http://lists.oasis-open.org/archives/dita/200911/msg00013.html (rollup by 
  Gershon. Closed?) 

> ACTION: All TC members who have not yet reviewed should do so ASAP and 
> respond on list.
> Bruce also needs answers to his questions in comments.
> TC needs to decide whether to replace the original topic with Bruce's one.
> CONTINUED. Revisit next week


New ITEM 3 November: Presence of @id affects processing 
* http://lists.oasis-open.org/archives/dita/200910/msg00135.html (Park) 

> Eliot: It's behavior specific for footnotes and is best captured on the <fn> 
> lang ref. It's not an arch spec issue.
> Jeff suggested some wording and Eliot feels that what Jeff did is fine.
> ACTION: Eliot to roll the comments up into the topic (<fn> lang spec topic).
> CLOSED.


New ITEM 3 November: When does applicability apply to key spaced termination? 
* http://lists.oasis-open.org/archives/dita/200911/msg00000.html (Kimber)

> Eliot: When you do key spaced construction (figuring out what the set of 
> effective keys is) processor can either filter out all topicrefs that are not
> applicable and then resolve the key definitions OR it can determine which key
> definitions are effective for all unique keys that have conditions and then 
> process. DITA-OT does the first approach mentioned. In editing and CMS 
> context, you may need to use the second approach, since you need to know all 
> the different things a key could resolve to. Need to make clear in the spec 
> that these 2 processing options are there and that the processor can do 
> either. Particular case is a topicref that's applicable to a condition that 
> does a topicref to a topicref that's applicable to a different condition. In 
> this case, whether you filter before or afterwards results in a different 
> resolution. Filtering before may result in no effective keyref definition. 
> My analysis is that all keys should be resolved before doing any filtering. 
> Also, for content referencing and filtering in general, the spec cannot 
> specify an order, because it never has. For the specific case of key 
> reference, which is a new feature and key space construction has to happen 
> before any other processing can happen, we can apply an order because it's a 
> new feature. 
> Eliot feels we must enforce an order in order to ensure compatibility 
> between processors.
> Jeff does not agree that filtering needs to happen after conref resolution. 
> Prefer to filter first to avoid having to process content that's going to be 
> thrown away. Eliot is saying that filtering early gives different results.
> Michael suggested an offline call to discuss further.
> ACTION: Michael to arrange the offline meeting.

> Keep meeting going for 2 hours next week if we have quorum next week (due to 
> DITA Europe)

> CONTINUED. Revisit next week.


New ITEM 3 November: Terminology for DITA 1.2 spec (concrete document type, 
local shell) 
* http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/200910/msg00140.html 
* http://lists.oasis-open.org/archives/dita/200911/msg00084.html (Eberlein update, in absentia) 

* Concrete document type 
  * Do we need this term? Is it a widely accepted term? 
  * How is a "Concrete document type" different from a "DITA document type"

* Local shell 
  * Content of <note> elements contentious

* Does the terminology apply to entire spec (including Lang Ref topics) or 
  only specific topics in the spec? 

> Eliot: DITA has to-date virtual document types which are not well defined. 
> These are defined by the @domains attribute. Concrete doc type is a shell or 
> root schema.
> Discussion...
> ACTION: Jeff to set up an offline call to hopefully progress on this item.


New ITEM 3 Nov: Key renaming 
* http://lists.oasis-open.org/archives/dita/200911/msg00016.html (Ogden/Kimber) 
* http://lists.oasis-open.org/archives/dita/200911/msg00049.html (Kudos to 
  Bruce for a brilliant literary insight into the nature of this debate!) 

> Eliot accepted Jeff's suggestion to use "key name" and has been implementing 
> it.
> CLOSED.


*** Meeting Adjourned ***