Re: [dita] Lightweight DITA spec: development strategy

Dear Kris and all,

In all honesty, this is not a concern about the lack of a fast track LwDITA movement, but about the expected alignment with DITA 2.0 (which has not gone through the OASIS approval process and probably won't go in the near future). 
We are aware of the approval requirements and we understand the need for alignment, but we were working under the idea of using the LwDITA spec as an experiment in the writing style and language to be used in 2.0... and not necessarily expecting alignment of sections beyond the short descriptions for elements/components as they are written in parallel.
The concern is more about having LwDITA chasing 2.0 in its process to become a standard, when 2.0 is not on the same track (fast or slow) in which LwDITA should be running.

Best,

Carlos

--Â

Carlos Evia, Ph.D.

Associate Professor of Communication

Chair, Hispanic/Latino Faculty & Staff Caucus

Virginia Tech

Blacksburg, VA 24061-0112

(540)200-8201

On Sun, Feb 3, 2019 at 9:27 PM Kristen James Eberlein <> wrote:

  
    
  
  

    
'm happy to discuss fast-tracking the LwDITA spec; I've been
      trying to do so since 2016 or earlier, beginning with insisting
      that the subcommittee issue the committee note. 

    
Two things:

    
      
It would be helpful for the TC to see the current state of the
        LwDITA spec. We understand that it is a draft document. I can
        create a PDF from the content in the LwDITA repo, if needed.

        

      

      
The LwDITA spec editors need to understand the reality of the
        spec approval timeline. The LwDITA spec needs to be approved by
        the TC and then sent through the OASIS process. After TC
        approval, there is a minimum of six months for the OASIS
        process, assuming NO need to modify the spec draft in any
          way. See
        https://www.oasis-open.org/apps/org/workgroup/dita/download.php/50807/Planning-DITA-1.3.pdf
        for more information.

    
    
 Please look at the PDF referenced above in order to understand
      the OASIS processes and the time frame that they impose.

    

    

    
Best,

      Kris

      

      Kristen James Eberlein

      Chair, OASIS DITA Technical Committee

      Principal consultant, Eberlein Consulting

      www.eberleinconsulting.com

      +1 919 622-1501; kriseberlein (skype)

      

    

    
On 2/3/2019 8:52 PM, Alan Houser wrote:

    

    Colleagues,
      

      

      I would like to tee up a discussion about Lightweight DITA spec
      development for Tuesday's DITA TC meeting.
      

      

      Adobe gave a demo of their Lightweight DITA support to a small
      group last Tuesday. What they showed was very encouraging ...
      support for XDITA authoring in the current release of Adobe
      FrameMaker, HDITA (LwDITA expressed in HTML5) in RoboHelp, and
      Lightweight DITA support in Adobe Experience Manager, Adobe's
      enterprise web CMS. Adobe is also deploying an internal workflow
      based on MDITA for customer-facing content. They used the
      Lightweight DITA Committee Note as the basis for their
      implementations.
      

      

      Carlos and I have asked Kris to open a dialog about tactics for
      fast-tracking the Lightweight DITA specification. We have
      increasing vendor support and adopter momentum, and fear that
      publishing a Lightweight DITA spec in 2020 or 2021 would risk
      irrelevance.
      

      

      Of course, Lightweight DITA must be compatible with DITA, and the
      DITA 2.0 specification is clearly on a different timetable. We
      trust this can be acknowledged and accommodated, without delaying
      the Lightweight DITA specification while DITA 2.0 spec development
      progresses.
      

      

      Carlos, Michael, and I (LwDITA spec editors) look forward to this
      discussion.
      

      

      -Alan
      

      

    
  

---------------------------------------------------------------------
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 

Attachment:
smime.p7s

Description: S/MIME Cryptographic Signature