Content model and specialization bases for hardware domain models

Hi, Zoe.

    
You and I talked a lot about this after the last TC meeting, and
      I thought it might be a good agenda item for today's TC call. And
      it'll close out an action item that is assigned to me.

    

    
Regarding the specialization base for <partno>, it
      needs to be <ph> (not <keyword>), if you want
      <partno> to be able to contain <data>. 

    

    
Also, Robert and I had a discussion about implementing a
        constraint to minimize the number of "strange" elements
      permitted (that is, the domain extensions that become available
      and seem so very bizarre to authors). We decided against it for
      the following reasons:

    
      
It would be a ton of work and only of use to people who use
        the document-type shells out-of-the-box.

      
We don't do this for any other domains.

    
    
I know I am the one who originally suggested that we consider a
      constraint, so I sincerely apologize for introducing the issue.
      (There is DITA 1.2 back history here; let's leave it at that!)

    
Regarding the content model for the elements ... I think
      we might want to simply define them directly, rather than using
      the already-defined entities. What do you (and reviewers and TC
      members) think of the following?

    
      
<hwcontrol>

      
        
Can contain the following: PCDATA, <data>,
          <draft-comment>, <image>, <keyword>,
          <partno>, <ph>, and <text>

        

      
      
<partno>

      
        
Can contain the following: PCDATA, <data>,
          <draft-comment>, <keyword>, and <text>

      
    
    
I have the DTD and RNG changes made and validated for these
      content models.

    

    
-- 

      Best,

      Kris

      

      Kristen James Eberlein

      Chair, OASIS DITA Technical Committee

      OASIS Distinguished Contributor

      Principal consultant, Eberlein Consulting LLC

      www.eberleinconsulting.com

      +1 919 622-1501; kriseberlein (skype)