This presentation demonstrates how typical difficulties in doing DITA Specialization can be overcome by using visual tooling.

1. Experts in Information Management Solutions and Services DITA Specialization: Tools for Visual SupportJune, 2010

4. People experienced with traditional ways of doing DITA Specialization willing to make this process more efficient

7. Main challenges

8. Traditional vs. Visual Specialization

9. Example / Demo

10. Q&A3

11. Traditional approach of doing DITA specializations 4

14. DefinitionsofattributesShell DTD1 Structural module 1 Structural module 3 Structural module 2 Domain module 1 … 5

15. Traditional way: Bottom-up approachII Specialized Model Shell DTD A Structural module A Domain module A Standard DITA Structural module 1 Structural module 3 Shell DTD1 Structural module 2 Domain module 1 Domain module 2 … Shell DTD2 6

16. Main challenges people face when doing DITA Specializations 7

19. Problems in setup of proper “empty” Shell DTD infrastructure

21. Automated DTD creation in the background9

23. Violating rules of DITA specialization*. Some examples:

24. Uniqueness of element names: Usage of same infotype or element names as in base DITA models

25. Structural elements without parent

26. Wrong element content model

28. Automatic validation of specialization rules

29. Disable operations that will lead to invalid model10 * see: http://support.ditaworks.com/problems_and_solutions/errors-in-dita-specializations-modeling/

31. Useintegrated tooling: no need for additional integration11

32. Traditional vs. Visual 12

35. Definitionsofattributes13

37. Most specialization functions are accessible from this presentationvia context menu

38. Changes made on current level of specialization are marked using color codes and icons:

39. Blue – changed/specialized element

40. Bold – changed cardinality

41. Red cross icon – removed elements 14

42. Example 15

44. Message Identifier

45. Message Main Text

46. Earthquake location

47. Earthquake Intensity level

48. Actions taken

49. Responses for operators for different cases (2 different cases for simplicity)

52. Step 2: Create main infrastructure components

53. Step 3: Perform structural specialization

54. Test results

55. Step 4: Perform domain specialization

56. Test results

57. Step 5: Consume model or Export17

58. DITAworks: specific terminology.. Standard DITA DITAworks Infotype Shell DTD Domain module Domain module Structural module Structural module 18

60. Modeling views:

61. Project explorer

62. Modules view

63. Domains view

64. Main visual editors:

65. Infotype editor

66. Structural Module editor

67. Domain editor19

71. Use Message Reference model as the parent or dependent model

73. Provide publicId

74. Create new structural module “eqMessage.stdmodule”

75. Choose required domains22

77. Alternatively, specialize elements using Structural module editor

82. As DITA Open toolkit plugin

83. As XML Schema (optional)25

84. Q & A Session 26

85. New Ideas in Information Management Sophienstr. 17 D-70178 Stuttgart phone: +49 (0) 711 - 99 33 85 90 fax: +49 (0) 711 - 99 33 85 99 e-mail: info@instinctools.com internet: www.instinctools.com 27

87. Export of managed specializations to DTD and XML Schema

88. Visual editors for DITA base model: Specialization editing

89. Model validations

90. Extended model:

91. Settings for editorial tools

92. WYSIWYG Style sheets

93. Custom validation rules

94. Custom transformations

96. Infrastructural project rules

97. Visual editors for DITA topics and maps

98. Link management

99. Content validation

100. Content refactoring (e.g. rename, move, content extraction etc.)

101. Reuse block management

102. Tag management

103. Versioning

105. Publishing configurations including settings for variables, conditional processing etc.

106. Extended support of Eclipse help

107. Export of content (full or partial)

108. Publishing server for running headless transformations.28

109. DITAworks Model-driven Architecture 29