[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita-techcomm] Prototype for a separate technical content specification
Hi Bob, Overall, I think it's on the right track. I think we will want a section on including or excluding element domains, since our goal is to modularize these and make it easier for folks to
include the elements they need in their shell DTD/schema. Thanks and best regards, --Scott Voting member: Boeing Data Standards Technical Advisory Board OASIS DocBook TC, Publishers SC (Chair) OASIS DITA TC, Tech Comm SC, LW DITA SC, Learning Content SC (Secretary) OASIS DITA Adoption TC OASIS Augmented Reality in Information Products (ARIP) TC Scott Hudson Jeppesen, A Boeing Company 55 Inverness Drive East Englewood, CO 80112 303-328-6228 | Cell: 303-350-7934 This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations. From:
<dita-techcomm@lists.oasis-open.org> on behalf of Bob Thomas <bob.thomas@tagsmiths.com> Hi, The attached PDF is my first attempt to pull the technical content in the DITA 1.3 specification into a separate specification. The cover, the filename, and the front matter are simply wrong so there's no need to
comment on that. Please also ignore any errata flagging artifacts. The primary purpose of this PDF is to show how this publication will be structured. With that in mind, there's no need to read the content in detail. Simply look at what's there and what isn't
and then share your thoughts. Best regards, -- Bob Thomas +1 720 201 8260 Skype: bob.thomas.colorado Instant messaging: Gmail chat (bob.thomas@tagsmiths.com) or Skype Time zone: Mountain (GMT-7) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]