DITA Technical Communication SC

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) Attachment: dita-v1.3-errata02-csd01-part2-tech-content-complete.pdf Description: Adobe PDF document

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
Content Strategist, Digital Aviation Learning and Development
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>
Date: Saturday, August 19, 2017 at 10:46 PM
To: DITA Tech Comm SC <dita-techcomm@lists.oasis-open.org>
Subject: [dita-techcomm] Prototype for a separate technical content specification


 


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)


 

Hi Scott, I think that doing something about including and excluding element domains is a great idea. However, I don't think that it belongs in the specification. A dedicated committee note would probably be a better channel for it. Best regards, Bob On Tue, Aug 22, 2017 at 11:05 AM, Scott Hudson < scott.hudson@jeppesen.com > wrote: 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 Content Strategist, Digital Aviation Learning and Development 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 > Date: Saturday, August 19, 2017 at 10:46 PM To: DITA Tech Comm SC < dita-techcomm@lists.oasis- open.org > Subject: [dita-techcomm] Prototype for a separate technical content specification   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)   -- 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)

I think this is a good starting point. Thanks for taking the time to start work on a prototype, Bob. I think the first places to begin work are the following: Restructure the element reference topics to follow the template established for the DITA 2.0 spec. This will highlight material that is inappropriate -- or material that really needs to be addressed in conceptual topics. Investigate whether any of these topics include normative statements. Remove unnecessary levels of nesting, most of which are artifacts of generating an all-inclusive edition. Figure out what exactly needs conceptual topics. I think most of the conceptual (old arch spec) topics about document types are pretty useless. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype) On 8/20/2017 12:46 AM, Bob Thomas wrote: 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) --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php