Re: [dita-lightweight-dita] Sample use case for the template-based specialization discussion

On 7/27/2015 10:13 AM, Don R. Day wrote:

    
      
      Of course, a transform exists that borrows on the use of
      @contentEditable directly, rather than a form. When you click on a
      button associated to a control, it reads the content out of the
      named elements and puts the values into POST variables which the
      server then uses, along with the @data-class values, to merge
      changed fields back into the original document. Mark Giffin, this
      is for you!

    
    

    Hi Don! I think I understand what you're describing here. This email
    and your previous one seem like a good fleshed-out example. Should I
    do something with it?

    

    Mark Giffin

    Mark Giffin Consulting, Inc.

    http://markgiffin.com/

    

    
      <article id="termdef_term">

      <h4><span class="editable" data-class="tloterm"
      contenteditable="true">Structured
      Content</span></h4><div
      data-class="body"><div data-class="topicbody">

          <div class="sectionTitle section">What is
      it?</div><div class="sectionContent"
      contenteditable="true" data-class="tlowhat">

                  <p>Content, whether in a textual, visual, or
      playable format, that conforms to structural and semantic rules
      that allow machine processing to meet specific business
      requirements.</p>

          </div>

          <div class="sectionTitle section">Why is it
      important?</div><div class="sectionContent"
      contenteditable="true" data-class="tlowhy">

                  <p>Humans are much better than computers when it
      comes to understanding the nuances of content. Structuring content
      with semantic metadata allows computers to understand the
      content’s relationship to business processes. This enables better
      discovery, marketing, and user engagement.</p>

          </div>

          <div class="sectionTitle section">Why does a technical
      communicator need to know this?</div><div
      class="sectionContent" contenteditable="true"
      data-class="tloessy">

                  <p>Readers understand the visual grammar of
      style in what they read in a browser or in print, but computers do
      not. Even for scanned pages converted into word processor files,
      the computer can only determine that something in a block of text
      is possibly a paragraph, but it cannot necessarily discern a
      paragraph from a note or a quotation. By indicating the order and
      intent of the parts of a document, writers ensure that publishing
      tools well into the future can usefully render that content, even
      if reading technologies change.</p>

                  <p>Adding structure to content adds both present
      and future value, turning content from a single-use commodity into
      a long-term asset. Content can be structured in a number of ways,
      although most commonly it is done by applying descriptive,
      codified markup to it (Extensible Markup Language (XML) or other
      semantic markup) or by storing content in named fields in a
      database.</p>

                  <p>Structured content clearly indicates not only
      the parts of the discourse (the titles, sections, lists, tables,
      and phrases that represent organization) but also the semantic
      intent of those containers. For example, paragraphs identified
      more specifically as quotations can be not only rendered
      differently for readers, but also made more easily discovered in
      searches for quotations or citations.</p>

          </div>

          <div class="sectionTitle
      section">Summary:</div><div class="sectionContent"
      contenteditable="true" data-class=""tlosummary>

              By structuring content appropriately, you can more easily
      turn information into knowledge, instructions into automation,
      concepts into lesson units, and more, thereby increasing its value
      to the business.

          </div>

        </div></div>

      </article>

      

      With appropriate CSS it looks like this (note that the field
      boundaries turn blue when you click a region to edit it):

      

      

      
-- 

        
        
 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  

      

      

      

      
      
        
          

                
            
              
 This email has been checked for
                viruses by Avast antivirus software. 

                www.avast.com