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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-adoption message

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


Subject: LwDITA Meeting Minutes for 15 May 2017


LwDITA Meeting Minutes for 15 May 2017

1 PM ET open

Present: Don Day, Michael Priestley, Carlos Evia, Rahel Bailie, Kris Eberlein, Mark Giffin, Keith Schengili-Roberts, Robert Anderson, Ullakaisa Kalander, Tim Grantham

Minutes for the last meeting were approved (with an amendment by Carlos Evia).

==Announcements==
===Updates to XDITA GitHub repository (see https://github.com/oasis-open/dita-lightweight)===
- fnref element has been deleted
- @width and @height attributes added to the video element as the result of a discussion Carlos had with Radu that these need to be present to render properly in HTML5
- @iframe attribute (with no/yes as possible values) to video element

==Report from STC Summit (Keith and Alan)==
- ~80 presentations, only four specifically mentioned "DITA" in their title
- Alan was called away, did not attend STC conference
- Keith was present, but did not attend many presentations as IXIASOFT colleague was sick and Keith had to be present at the company booth
- about 40-45 people attended Keith's presentation (relatively well-attended) on the business reasons why companies and their tech doc teams tend to move to DITA
- some good questions came up afterwards, including ones about migrating from FrameMaker and Flare to DITA
- one query about how imminent DITA 2.0 is and whether they should hold off on migrating to DITA until it is launched; Keith currently writing a blog piece explaining how DITA 2.0 should not be thought of as being equivalent to a software upgrade
- Mark commented that at the previous STC conference in Phoenix they did not have a lot of DITA-related sessions either; Alan agreed and added that the mandate of the STC is to provide a wider range of more broadly-defined topics, designed to appeal to broad range of technical expertise and issues
- There was another comment that the LavaCon conferences have more of an interest in Content Strategy and so are more business-inclined that technically-inclined
- Michael commented that he has received some brutal reviews from previous STC conferences, as attendees are looking for more polished speakers, and that there is some backlash to DITA in general; this creates a more problematic audience to program for

==Internal DITAweb review of Committee Note==
===Defining LwDITA as its own standard or not just "slimmed-down" DITA (Alan Houser)===
- Carlos asked Alan to talk about his proposal on how to describe LwDITA; is seeking a clear distinction of what LwDITA is and for what use cases is it appropriate and where it is not
- Alan expressed a preference for "simplified" as opposed to "slimmed-down".
- Kris commented that LwDITA is perceived as a simplified sub-set of full DITA (XDITA), enables the use of DITA in other authoring formats (HDITA, MDITA) and to other formats in the future, and that LwDITA is also designed to be an aid in collaboration efforts between members of documentation departments and other content contributors within an organization
- request was made in section one to change "robust XML structures" -> "advanced XML features"
- Michael suggested an email be sent to the group about wording changes to the "Why Lightweight DITA?" section. Kris will look at it and comment.

===Discuss the footnote structure in LwDITA (mainly XDITA and how it does not map well to HDITA and MDITA)===
- Rahel noted that for anyone working within a regulated industry, disclaimers are common, as is the need for footnotes
- Carlos asked how this could be mapped to MDITA and HDITA, while noting that the "use by reference" model is what is used within HTML5 instead of a more generated footnote
- Michael suggested that since we are on the hook for interoperability, we ought to aim for the most-typically used solution when possible
- Robert suggested that we have people add footnotes to the end of the topic, so people do not think of it as an inline element that auto-generates content at the end of a page; however, this cannot be done without creating a new container element
- Carlos will try to articulate the points brought up during the discussion and add them to a recrafted version of the spec that covers this element.

2:04 PM ET close




Cheers!

 

-

Keith Schengili-Roberts
Market Researcher and DITA Evangelist
 
IXIASOFT 
825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
tel  + 1 514 279-4942  /  toll free + 1 877 279-4942 




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