RE: [dita-fa-edboard] Creating content for DITA Learning SC

[Don Day <dond@us.ibm.com>]

Bruce, the TC's wiki site is publicly visible and has the appropriate
member authorization for accessing the edit controls on pages. The DITA
Roadmap document on the site is an example of a document expressly created
for public visibility. Sure, the interface is not as exciting as that at
dita.xml.org, but it is functional and clearly identifies the site as the
DITA TC's purview. So I think I am persuaded by Mary's appeal to try the
equivalent pages there. What remains for the DITA FA then is to provide
some easy-to-find jump page that can link back to any of the TC's Wiki
materials that we want to be easily discoverable from the FA.

Regards,
--
Don Day
Chair, OASIS DITA Technical Committee
IBM Lead DITA Architect
Email: dond@us.ibm.com
11501 Burnet Rd. MS9033E015, Austin TX 78758
Phone: +1 512-838-8550
T/L: 678-8550

"Where is the wisdom we have lost in knowledge?
 Where is the knowledge we have lost in information?"
   --T.S. Eliot


                                                                           
             "Esrig, Bruce                                                 
             \(Bruce\)"                                                    
             <esrig@lucent.com                                          To 
             >                         <mary.mcrae@oasis-open.org>, "Carol 
                                       Geyer" <carol.geyer@oasis-open.org> 
             10/18/2006 07:33                                           cc 
             AM                        <dita-fa-edboard@lists.xml.org>,    
                                       John Hunt/Cambridge/IBM@Lotus,      
                                       <scott.hudson@flatironssolutions.co 
                                       m>                                  
                                                                   Subject 
                                       RE: [dita-fa-edboard] Creating      
                                       content for DITA Learning SC        
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Hi Mary,

Yes, it would be nice to have some more advice in an appropriate forum on
the kinds of information that the SC develops, where information would be
first recorded, and where summaries would be stored.

The impetus was that we have an increasing number of major threads in the
conversation on the SC, and a wiki seems like a good place to record
summaries of what we've learned. The e-mail threads are too scattered to
enable observers and new members (or in some cases, existing members who
have lots of e-mail messages flying by) to establish a stable vision of
what the SC is doing and needs to do next.

Is the wiki at http://wiki.oasis-open.org/dita/LearningSubcommittee
publicly visible?
Is it editable only by TC members?

We've put some global design effort into the dita.xml.org site, which makes
it a visually appealing site, but I can understand the benefit from an
intellectual property point of view of making sure that contributions are
represented in the wiki.oasis-open.org site or in other documents on
www.oasis-open.org.

Best wishes,

Bruce Esrig

      From: Mary McRae [mailto:mary.mcrae@oasis-open.org]
      Sent: Wednesday, October 18, 2006 8:05 AM
      To: Esrig, Bruce (Bruce); 'Carol Geyer'
      Cc: dita-fa-edboard@lists.xml.org; john_hunt@us.ibm.com;
      scott.hudson@flatironssolutions.com
      Subject: RE: [dita-fa-edboard] Creating content for DITA Learning SC

      Hi everyone,

        It's great to see an overview of the Learning Content SC on
      dita.xml.org! I think that's a good use of the focus area, and should
      definitely give the subcommittee more exposure and potentially garner
      more recruits. There is a difference, however, in work products of
      the subcommittee vs work published on the focus area. Each TC/SC
      already has a number of publicly-accessible workplaces that are
      controlled by our policies and procedures and all work must be
      carried on in those areas. Creating links to those approved areas
      from the focus area is certainly acceptable, but the Drupal sites do
      not have the permission controls that restrict contributions to
      members nor do they guarantee permanence.

      Remember that the subcomittee is not authorized to approve work
      products; a subcommittee typically consists of a team of experts in a
      particular area that work to produce draft materials that are then
      submitted to the main technical committee for discussion and
      approval. Anyone who is not a member (and this explicitly excludes
      observers) of the technical committee cannot contribute work except
      through our comment facility - this is for IPR reasons.

      I hope this helps clarify - feel free to contact me with any
      questions!

      Regards,

      Mary

      ---------------------------------------------------
      Mary P McRae
      Manager of TC Administration, OASIS
      email: mary.mcrae@oasis-open.org
      web: www.oasis-open.org
      phone: 603.232.9090

      Register for OASIS Adoption Forum:
      "Managing Secure Interactions in Sector Applications"
      28 - 29 Nov 2006, London
      www.oasis-open.org/events/adoptionforum2006/




       From: Esrig, Bruce (Bruce) [mailto:esrig@lucent.com]
       Sent: Wednesday, October 18, 2006 7:45 AM
       To: Carol Geyer
       Cc: dita-fa-edboard@lists.xml.org; john_hunt@us.ibm.com;
       scott.hudson@flatironssolutions.com
       Subject: [dita-fa-edboard] Creating content for DITA Learning SC

       Hi Carol,

       John Hunt, Scott Hudson, and I created a little tree of pages for
       the DITA Learning Content Subcommittee (SC).

       You can see our progress at
       http://dita.xml.org/wiki-LearningContentSC, its subordinate pages
       (three links in the list of questions), and the See also pages.

       1. For now, these pages are on the wiki. That will let the entire SC
       add info to them. (Oh, maybe a better way is to make them Knowledge
       Base pages and temporarily open up the permissions on those pages.)
       There's a big note under Editorial Guidelines stating that the work
       of the SC would be done at the main OASIS site, so I'd like to
       confirm that the following policy is ok. The SC pages at
       dita.xml.org are for capturing and reporting publicly-visible
       status. We've still got the SC wiki at the main OASIS site for
       working information such as the agenda, and we would still use the
       e-mail list for contributions.

       (Thinking ahead ...) It's possible that John Hunt and Scott H. would
       want to join the editorial board. Scott H. has already written a
       message about that to the communications e-mail address. I'd imagine
       that there will be at least a technical requirement for people such
       as SC chairs and secretaries to have editorial permissions to edit
       pages once they move to the Knowledge Base. And it appears that an
       editor can put a wiki page into "the book" using a drop-down menu.
       Does that simultaneously change the permissions ... oh, probably not
       ... can the permissions change be done separately and manually using
       the permissions settings on the page? I might regret putting "wiki-"
       in the URLs ... I'm still looking for some way that a user can know
       whether they're in the Knowledge Base, DITA Today, or DITA wiki just
       by looking at the page.

       2. While explaining how to add new pages, I mentioned some rules
       that needed to be documented. To capture that, I added some info
       under Editorial Guidelines. See About -> Editorial Guidelines and
       its subordinate pages. Also the main pages for DITA Today and the
       wiki (the only substantive change on those two pages is to add a
       sentence referring to the Editorial Guidelines and the Style Guide).

       3. Also, as far as page navigation is concerned, the About link in
       the top right corner goes to a different location from the About
       section in the lower right. The upper right goes to a common set of
       policies for the XML.org online communities. The lower right goes to
       the dita.xml.org version. As far as I can tell, the dita.xml.org
       version is (now) more mature and consistent than the common set. So
       some reconciliation is needed. The common policy area takes the
       reader out of the DITA site, and I'd rather stay within the DITA
       site, but perhaps as the number of sites grows, that would be
       unmanageable.

       Best wishes,

       Bruce