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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-busdocs message

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


Subject: Re: [dita-busdocs] March 1 2010 Regular Meeting Minutes


Hi Bruce,

  You should not use the word 'charter'; you might also want to make it clear that your deliverables are to the TC only - that is, a subcommittee cannot make any binding decisions on behalf of the main TC and all work needs to be approved.

  Hope that helps!

Mary

Mary P McRae
Director, Standards Development
Technical Committee Administrator
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org 
web: www.oasis-open.org
twitter: @fiberartisan  #oasisopen
phone: 1.603.232.9090

Standards are like parachutes: they work best when they're open.



On Mar 1, 2010, at 5:14 PM, Bruce Nevin (bnevin) wrote:

> I guess by "charter" you mean the goals and deliverables listed under
> "Group Notes". Should we slip in a main title that says "Subcommittee
> Charter"?
> 
> Under goals, #4 is 
> 	Long term, to develop and recommend guidance for organizations 
> 	that intend to adopt DITA for enterprise business documents. 
> Under deliverables, #4 is 
> 	Long term, recommended guidance for implementing DITA for 
> 	enterprise business documents.
> The Help SC has hit on the notion of cloning itself as a SC of the
> Adoption TC, and this seems to have got a favorable response. We should
> plan to do that. 
> 
> The statement of officers belongs in another place. If there is no other
> place than "Group Notes" then put it at the top (before the main title,
> if you do that):
> 
> Co-chairs: Ann Rockley, The Rockley Group; Michael Boses, In.vision
> Research 
> 
> The relationship between goals and deliverables is clearer if
> corresponding items are listed in the same order and have the same
> number, so that for each goal there are one or more documents or other
> products identified as deliverables. Also, the tentative hedge phrases
> can go away. We're no longer just getting started. Here's a suggested
> revision:
> 
> Goals: 
> 
> 1. Develop and recommend a metamodel for enterprise business documents
> which 
> * Characterizes the range of documents addressed by this subcommittee.
> * Identifies properties of these documents relevant to their treatment
> in the DITA standard. 
> 
> 2. Develop and recommend an approach to harmonizing the enterprise
> business document metamodel with the DITA standard. 
> 
> 3. Develop and recommend a standard approach for fully expanding DITA
> Map references into an editable process instance that may be validated
> against an approved DITA DTD or schema, without compromising content
> management and reuse. 
> 
> 4. Long term, to develop and recommend guidance for organizations that
> intend to adopt DITA for enterprise business documents. 
> 
> Deliverables:  
> 
> 1. Recommended baseline enterprise business document metamodel. 
> 
> 2. Recommended harmonization of enterprise business document metamodel
> with the DITA Standard.
> 
> 3. Recommended approach for fully expanding DITA Map references into a
> valid editable process instance. 
> 
> 4. Long term, recommended guidance for implementing DITA for enterprise
> business documents.
> 
> I'll have some comments on the backgrounder.
> 
> 	/Bruce
> 
>> -----Original Message-----
>> From: mboses@quark.com [mailto:mboses@quark.com] 
>> Sent: Monday, March 01, 2010 1:17 PM
>> To: dita-busdocs@lists.oasis-open.org
>> Subject: [dita-busdocs] March 1 2010 Regular Meeting Minutes
>> 
>> 10:00 am  11:55 am EST 
>> 
>> In attendance:
>> 
>> Bruce Nevin
>> Tim Grantham
>> Rob Hanna
>> Steve Manning
>> Josef Pellizzari
>> Zarella Rendon
>> Michael Boses
>> 
>> Agenda
>> 
>>  1. Open action item: Aggregated authoring paper.
>> 
>> There was discussion concerning the current status of the 
>> paper as well as the target audience. The purpose of the 
>> paper is to express the requirements for aggregated 
>> authoring, and to facilitate feedback from authoring vendors 
>> as to their ability to support these requirements today or 
>> their concerns, if any, over the requirements. Steve will 
>> upload a draft of the paper to the OASIS site this week.
>> 
>>  2. Continuing Discussion: BusDocs relationship to other 
>> committees/subcommittees and upcoming projects and goals.
>> 
>> There was discussion concerning whether the BusDocs charter 
>> and backgrounder sufficiently reflects the activities of the 
>> committee. Michael will add a link to these documents to the 
>> minutes. All members of the subcommittee are asked to review 
>> the documents again so that we can discuss this at the next 
>> regularly scheduled subcommittee meeting on March 15, 2010.
>> 
>> A specific question to consider when reading the documents is 
>> whether they address documents that would normally be created 
>> with a structured lifecycle that includes versioning, 
>> reviews, and approval.  
>> 
>> Charter: 
>> http://www.oasis-open.org/apps/org/workgroup/dita-busdocs/index.php
>> 
>> Backgrounder: 
>> http://www.oasis-open.org/committees/download.php/25981/DITA%2
>> 0for%20Enterprise%20Business%20Documents%20Sub-committee%20Bac
>> kground.pdf
>> 
>> 3. Consensus on date for Mary to join the meeting.
>> 
>> Deferred this to the March 15, 2010 meeting when more members 
>> of the subcommittee will be present to decide on best date.
>> 
>> 4. Enterprise Use Case for Interoperability of Content 
>> 
>> Michael will send an email on OASIS to start a discussion 
>> that will use a very generic product development lifecycle as 
>> an enterprise use case.
>> 
>> 5. Business Document Meta Model
>> 
>> Rob will post the first draft of his meta model document to 
>> OASIS along with the comments that were accumulated on Basecamp. 
>> 
>> 6. Migration of Basecamp
>> 
>> Discussion continued on the migration of content from 
>> Basecamp to the OASIS site. Steve and Rob suggested that all 
>> of the content on Basecamp should be moved.
>> 
>> Regards,
>> 
>> Michael
>> 
> 
> ---------------------------------------------------------------------
> 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
> 



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