[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OPML and DITA Maps
This is a comment tossed out purely for the long look ahead. Notably, OPML also represents markup for stateful information
about the active location in a list. I think the intent was to
ensure that the presentation of a list could be picked up again in
the same state later on or at a different location. This part is
clutter to that spec--it is antithetical to the RESTful way of
thinking, so don't let that part distract you. The useful essence
is:
So this note is for adding to the list of considerations for DITA
2.0-era architecture. [2] https://checkvist.com/ (I use the free version to develop my presentation outlines, then transform to DITA map to generate stubs for slides--works great) [3] https://github.com/ilikenwf/nestedSortable, https://github.com/dbushell/Nestable [4] http://www.netcrucible.com/xslt/opml.htm --
Don R. Day
Founding Chair, OASIS DITA Technical Committee LinkedIn: donrday Twitter: @donrday About.me: Don R. Day Skype: don.r.day
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?" --T.S. Eliot
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]