diff --git a/catalog.xml b/catalog.xml
new file mode 100644
index 0000000..d4632e6
--- /dev/null
+++ b/catalog.xml
@@ -0,0 +1,79 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/dtd/concept.dtd b/dtd/concept.dtd
new file mode 100644
index 0000000..a797ce8
--- /dev/null
+++ b/dtd/concept.dtd
@@ -0,0 +1,74 @@
+
+
+
+
+
+
+ %ui-d-dec;
+
+ %hi-d-dec;
+
+ %pr-d-dec;
+
+ %sw-d-dec;
+
+ %ut-d-dec;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ %topic-type;
+
+
+
+ %concept-typemod;
+
+
+
+
+ %ui-d-def;
+
+ %hi-d-def;
+
+ %pr-d-def;
+
+ %sw-d-def;
+
+ %ut-d-def;
+
diff --git a/dtd/concept.mod b/dtd/concept.mod
new file mode 100644
index 0000000..3587864
--- /dev/null
+++ b/dtd/concept.mod
@@ -0,0 +1,63 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/ditabase.dtd b/dtd/ditabase.dtd
new file mode 100644
index 0000000..89a8cea
--- /dev/null
+++ b/dtd/ditabase.dtd
@@ -0,0 +1,91 @@
+
+
+
+
+
+
+ %ui-d-dec;
+
+ %hi-d-dec;
+
+ %pr-d-dec;
+
+ %sw-d-dec;
+
+ %ut-d-dec;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ %topic-type;
+
+
+
+ %concept-typemod;
+
+
+
+ %task-typemod;
+
+
+
+ %reference-typemod;
+
+
+
+
+ %ui-d-def;
+
+ %hi-d-def;
+
+ %pr-d-def;
+
+ %sw-d-def;
+
+ %ut-d-def;
+
+
+
+
+
diff --git a/dtd/highlight-domain.ent b/dtd/highlight-domain.ent
new file mode 100644
index 0000000..fd844be
--- /dev/null
+++ b/dtd/highlight-domain.ent
@@ -0,0 +1,25 @@
+
+
+
+
+
diff --git a/dtd/highlight-domain.mod b/dtd/highlight-domain.mod
new file mode 100644
index 0000000..49bb872
--- /dev/null
+++ b/dtd/highlight-domain.mod
@@ -0,0 +1,63 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/map.dtd b/dtd/map.dtd
new file mode 100644
index 0000000..d08bed5
--- /dev/null
+++ b/dtd/map.dtd
@@ -0,0 +1,40 @@
+
+
+
+ %mapgroup-d-dec;
+
+
+
+
+
+
+
+
+
+ %map-type;
+
+
+
+
+ %mapgroup-d-def;
diff --git a/dtd/map.mod b/dtd/map.mod
new file mode 100644
index 0000000..60dfa8c
--- /dev/null
+++ b/dtd/map.mod
@@ -0,0 +1,219 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ %metaXML;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/mapgroup.ent b/dtd/mapgroup.ent
new file mode 100644
index 0000000..b58f27c
--- /dev/null
+++ b/dtd/mapgroup.ent
@@ -0,0 +1,25 @@
+
+
+
+
diff --git a/dtd/mapgroup.mod b/dtd/mapgroup.mod
new file mode 100644
index 0000000..1f896e0
--- /dev/null
+++ b/dtd/mapgroup.mod
@@ -0,0 +1,44 @@
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/meta_xml.mod b/dtd/meta_xml.mod
new file mode 100644
index 0000000..b23c686
--- /dev/null
+++ b/dtd/meta_xml.mod
@@ -0,0 +1,171 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/programming-domain.ent b/dtd/programming-domain.ent
new file mode 100644
index 0000000..35b71d7
--- /dev/null
+++ b/dtd/programming-domain.ent
@@ -0,0 +1,29 @@
+
+
+
+
+
+
+
+
+
diff --git a/dtd/programming-domain.mod b/dtd/programming-domain.mod
new file mode 100644
index 0000000..cbf13c6
--- /dev/null
+++ b/dtd/programming-domain.mod
@@ -0,0 +1,246 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/reference.dtd b/dtd/reference.dtd
new file mode 100644
index 0000000..344f948
--- /dev/null
+++ b/dtd/reference.dtd
@@ -0,0 +1,74 @@
+
+
+
+
+
+
+ %ui-d-dec;
+
+ %hi-d-dec;
+
+ %pr-d-dec;
+
+ %sw-d-dec;
+
+ %ut-d-dec;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ %topic-type;
+
+
+
+ %reference-typemod;
+
+
+
+
+ %ui-d-def;
+
+ %hi-d-def;
+
+ %pr-d-def;
+
+ %sw-d-def;
+
+ %ut-d-def;
diff --git a/dtd/reference.mod b/dtd/reference.mod
new file mode 100644
index 0000000..33e97ec
--- /dev/null
+++ b/dtd/reference.mod
@@ -0,0 +1,143 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/software-domain.ent b/dtd/software-domain.ent
new file mode 100644
index 0000000..55ed5cf
--- /dev/null
+++ b/dtd/software-domain.ent
@@ -0,0 +1,27 @@
+
+
+
+
+
+
+
diff --git a/dtd/software-domain.mod b/dtd/software-domain.mod
new file mode 100644
index 0000000..6c3e892
--- /dev/null
+++ b/dtd/software-domain.mod
@@ -0,0 +1,86 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/task.dtd b/dtd/task.dtd
new file mode 100644
index 0000000..c784ff8
--- /dev/null
+++ b/dtd/task.dtd
@@ -0,0 +1,73 @@
+
+
+
+
+
+
+ %ui-d-dec;
+
+ %hi-d-dec;
+
+ %pr-d-dec;
+
+ %sw-d-dec;
+
+ %ut-d-dec;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ %topic-type;
+
+
+
+ %task-typemod;
+
+
+
+ %ui-d-def;
+
+ %hi-d-def;
+
+ %pr-d-def;
+
+ %sw-d-def;
+
+ %ut-d-def;
diff --git a/dtd/task.mod b/dtd/task.mod
new file mode 100644
index 0000000..8894f06
--- /dev/null
+++ b/dtd/task.mod
@@ -0,0 +1,246 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/tbl_xml.mod b/dtd/tbl_xml.mod
new file mode 100644
index 0000000..182bde1
--- /dev/null
+++ b/dtd/tbl_xml.mod
@@ -0,0 +1,139 @@
+
+
+
+
+
+
+]]>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/topic.dtd b/dtd/topic.dtd
new file mode 100644
index 0000000..d113a98
--- /dev/null
+++ b/dtd/topic.dtd
@@ -0,0 +1,71 @@
+
+
+
+
+
+
+ %ui-d-dec;
+
+ %hi-d-dec;
+
+ %pr-d-dec;
+
+ %sw-d-dec;
+
+ %ut-d-dec;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ %topic-type;
+
+
+
+
+
+
+ %ui-d-def;
+
+ %hi-d-def;
+
+ %pr-d-def;
+
+ %sw-d-def;
+
+ %ut-d-def;
diff --git a/dtd/topic.mod b/dtd/topic.mod
new file mode 100644
index 0000000..fb5f5d0
--- /dev/null
+++ b/dtd/topic.mod
@@ -0,0 +1,611 @@
+
+
+
+
+
+
+
+
+
+
+
+
+ %topicDefns;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ %tableXML;
+
+
+
+ %metaXML;
+
+
+
+ %topicClasses;
diff --git a/dtd/topic_class.ent b/dtd/topic_class.ent
new file mode 100644
index 0000000..19bf3ef
--- /dev/null
+++ b/dtd/topic_class.ent
@@ -0,0 +1,83 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/topic_defn.ent b/dtd/topic_defn.ent
new file mode 100644
index 0000000..e3f3ba6
--- /dev/null
+++ b/dtd/topic_defn.ent
@@ -0,0 +1,119 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/ui-domain.ent b/dtd/ui-domain.ent
new file mode 100644
index 0000000..e29dc39
--- /dev/null
+++ b/dtd/ui-domain.ent
@@ -0,0 +1,27 @@
+
+
+
+
+
+
+
diff --git a/dtd/ui-domain.mod b/dtd/ui-domain.mod
new file mode 100644
index 0000000..7aca5b7
--- /dev/null
+++ b/dtd/ui-domain.mod
@@ -0,0 +1,72 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/dtd/utilities-domain.ent b/dtd/utilities-domain.ent
new file mode 100644
index 0000000..6dae01d
--- /dev/null
+++ b/dtd/utilities-domain.ent
@@ -0,0 +1,25 @@
+
+
+
+
+
diff --git a/dtd/utilities-domain.mod b/dtd/utilities-domain.mod
new file mode 100644
index 0000000..c97640b
--- /dev/null
+++ b/dtd/utilities-domain.mod
@@ -0,0 +1,77 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/plugin.xml b/plugin.xml
new file mode 100644
index 0000000..616e78c
--- /dev/null
+++ b/plugin.xml
@@ -0,0 +1,8 @@
+
+
+
+
+
diff --git a/schema/concept.grp b/schema/concept.grp
new file mode 100644
index 0000000..9fb3534
--- /dev/null
+++ b/schema/concept.grp
@@ -0,0 +1,15 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/concept.mod b/schema/concept.mod
new file mode 100644
index 0000000..d3fdfc2
--- /dev/null
+++ b/schema/concept.mod
@@ -0,0 +1,67 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/concept.xsd b/schema/concept.xsd
new file mode 100644
index 0000000..f325d1e
--- /dev/null
+++ b/schema/concept.xsd
@@ -0,0 +1,55 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/ditabase.xsd b/schema/ditabase.xsd
new file mode 100644
index 0000000..c4db87a
--- /dev/null
+++ b/schema/ditabase.xsd
@@ -0,0 +1,104 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element allows you to combine several articles into a single
+XML file. You can mix the article types after the DITA element. For example,
+you can start with an introductory topic, continue with concept and task information,
+and conclude with reference information. You can create several peer articles
+at the main level, and create heierarchies under each main article.
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/highlight-domain.mod b/schema/highlight-domain.mod
new file mode 100644
index 0000000..2da0d46
--- /dev/null
+++ b/schema/highlight-domain.mod
@@ -0,0 +1,96 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/map.grp b/schema/map.grp
new file mode 100644
index 0000000..4c42160
--- /dev/null
+++ b/schema/map.grp
@@ -0,0 +1,81 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/map.mod b/schema/map.mod
new file mode 100644
index 0000000..f3d0cd0
--- /dev/null
+++ b/schema/map.mod
@@ -0,0 +1,420 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Select attributes is a parameter entity declaration in the topic DTD that includes
+attributes whose values may be used for affecting the display of a topic or its
+selection by search tools.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ID attributes is a parameter entity declaration in the topic DTD that includes
+attributes whose values may be used for conditional processing or for selection by
+search tools.
+
+
+
+
+
+
+
+ Universal attributes is a parameter entity declaration in the topic DTD that
+includes all of the attributes in the select-atts and id-atts attribute groups.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/map.xsd b/schema/map.xsd
new file mode 100644
index 0000000..eaae714
--- /dev/null
+++ b/schema/map.xsd
@@ -0,0 +1,23 @@
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/mapgroup.mod b/schema/mapgroup.mod
new file mode 100644
index 0000000..e39f695
--- /dev/null
+++ b/schema/mapgroup.mod
@@ -0,0 +1,65 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/meta_xml.grp b/schema/meta_xml.grp
new file mode 100644
index 0000000..437129b
--- /dev/null
+++ b/schema/meta_xml.grp
@@ -0,0 +1,78 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/meta_xml.mod b/schema/meta_xml.mod
new file mode 100644
index 0000000..327b318
--- /dev/null
+++ b/schema/meta_xml.mod
@@ -0,0 +1,458 @@
+
+
+
+
+
+
+ This metadata element can contain the name and address of the topic's
+author, or it can be left empty and point to another location where the author
+is defined.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a reference to a resource from which the present
+topic is derived, either completely or in part. The reference can be a string
+or a cross-reference.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This metadata element contains the name of the person, company,
+or organization responsible for making the resource available.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This is the container element for a single copyright entry. It includes
+the copyright years and the copyright holder. Multiple <copyright> statements
+are allowed.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This empty element contains the copyright date or dates as specified
+by the year attribute.
+
+
+
+
+
+
+
+
+
+
+ This element indicates the ownership of the information contained
+in the topic.
+
+
+
+
+
+
+
+
+
+
+
+ This element contains the critical dates in a document life cycle,
+such as the creation, revision, and publication dates.
+
+
+
+
+
+
+
+
+
+
+
+
+ This empty prolog element contains tracking dates that are important
+in a topic development cycle.
+
+
+
+
+
+
+
+
+
+
+
+
+ This empty element specifies the document creation date using the
+date attribute.
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+ This empty metadata element indicates the intended audience for a
+topic using its type attribute. Since a topic can have multiple audiences,
+you can include multiple audience elements. For each audience you specify,
+you can identify the high-level task they are trying to accomplish (job) and
+the level of experience expected.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element can represent any category by which a topic might
+be classified for retrieval or navigation; for example, the categories could
+be used to group topics in a generated navigation bar. Topics can belong to
+multiple categories.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ An index entry. You can nest entries to create multi-level indexes.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a list of keywords, separated by commas, that
+can be used by a search engine.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Identifies a key word of some sort. Can be used in specialized topic
+types as a base for particular kinds of keywords, which can then be processed
+in particular ways (formatted differently, automatically indexed, etc.). If
+the keyref attribute is used, the keyword may be turned into a hyperlink on
+output.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element can be used to identify properties not otherwise included
+in <metadata> and assign property/pair values to those properties. The
+name attribute identifies the property and the content attribute specifies
+the property's value.
+
+
+
+
+
+
+
+
+
+
+
+
+ This empty prolog element can indicate any preferred controls for
+access to a topic. Permissions can be used as viewing filters. Standard DITA
+processing does not use this element.
+
+
+
+
+
+
+
+
+
+ This metadata element in the prolog contains information about the
+product or products that are the subject matter of the current topic.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element indicates the manufacturer or brand associated with
+the current product.
+
+
+
+
+
+
+
+
+
+
+
+ This metadata element contains information about the product series
+that the topic supports.
+
+
+
+
+
+
+
+
+
+
+
+ This metadata element contains a description of the operating system
+and hardware that comprise a platform.
+
+
+
+
+
+
+
+
+
+
+
+ This metadata element identifies the program number of the associated
+program product. This is typically an order number or a product tracking
+code that could be replaced by an order number when a product completes development.
+
+
+
+
+
+
+
+
+
+
+
+ This element contains the feature number of a product in the document
+metadata.
+
+
+
+
+
+
+
+
+
+
+
+ This element is used to identify a piece of documentation or of a
+product which is associated with the current topic. For example, a product
+might be made up of many components, each of which is installable separately.
+Components might also be shared by several products so that the same component
+could be available for installation with many products. This identification
+could be used to check cross-component dependencies when some components are
+installed and not others. http://www.w3.org/TR/REC-html40/struct/objects.html
+
+
+
+
+
+
+
+
+
+
+
+ This metadata element contains the names of the products that are
+supported by the information in this topic.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This is the container for a list (<vrm>) containing the version,
+release, and.modification information for multiple products or versions of
+products to which the topic applies.
+
+
+
+
+
+
+
+
+
+
+
+ This empty element contains information about a single product's
+version,.modification, and release, to which the current topic applies.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/programming-domain.mod b/schema/programming-domain.mod
new file mode 100644
index 0000000..b13a577
--- /dev/null
+++ b/schema/programming-domain.mod
@@ -0,0 +1,495 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/reference.grp b/schema/reference.grp
new file mode 100644
index 0000000..4617fa8
--- /dev/null
+++ b/schema/reference.grp
@@ -0,0 +1,76 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/reference.mod b/schema/reference.mod
new file mode 100644
index 0000000..3001087
--- /dev/null
+++ b/schema/reference.mod
@@ -0,0 +1,186 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/reference.xsd b/schema/reference.xsd
new file mode 100644
index 0000000..e058d12
--- /dev/null
+++ b/schema/reference.xsd
@@ -0,0 +1,55 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/relnotes_schema.txt b/schema/relnotes_schema.txt
new file mode 100644
index 0000000..d347e8a
--- /dev/null
+++ b/schema/relnotes_schema.txt
@@ -0,0 +1,4 @@
+This DITA release includes an implementation of the topic architecture in
+XML Schema. The DTDs are still the canonical representation of DITA. The
+design pattern for the DITA Schemas is based on the W3C XML Schema 1.0
+Specification and may be subject to change in the future.
diff --git a/schema/software-domain.mod b/schema/software-domain.mod
new file mode 100644
index 0000000..1b82019
--- /dev/null
+++ b/schema/software-domain.mod
@@ -0,0 +1,144 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/task.grp b/schema/task.grp
new file mode 100644
index 0000000..30fe8fb
--- /dev/null
+++ b/schema/task.grp
@@ -0,0 +1,153 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/task.mod b/schema/task.mod
new file mode 100644
index 0000000..c909e19
--- /dev/null
+++ b/schema/task.mod
@@ -0,0 +1,361 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/task.xsd b/schema/task.xsd
new file mode 100644
index 0000000..f1aebdb
--- /dev/null
+++ b/schema/task.xsd
@@ -0,0 +1,59 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/tbl_xml.grp b/schema/tbl_xml.grp
new file mode 100644
index 0000000..1e326a1
--- /dev/null
+++ b/schema/tbl_xml.grp
@@ -0,0 +1,60 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/tbl_xml.mod b/schema/tbl_xml.mod
new file mode 100644
index 0000000..d403709
--- /dev/null
+++ b/schema/tbl_xml.mod
@@ -0,0 +1,228 @@
+
+
+
+
+
+
+
+ The container element for CALS table elements. See <simpletable>
+for a simplified table.model.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The element in a <table> that contains column, row, spanning,
+header and footer specifications, and the body (<tbody>) of the table.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a column specification for a table, including
+assigning a column name and number, cell content alignment, and column width.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A span specification in a table column or row specifies how two or
+more cells are to be combined.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This table header element precedes the table body (<tbody>) element.
+ It is currently not used.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This table footer element precedes the <table> body (<tbody>)
+element. It is currently not used.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains the rows in a <table>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a single row in a table <tgroup>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element defines an entry (a single cell) in a table row.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/topic.grp b/schema/topic.grp
new file mode 100644
index 0000000..eb0c87f
--- /dev/null
+++ b/schema/topic.grp
@@ -0,0 +1,365 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/topic.mod b/schema/topic.mod
new file mode 100644
index 0000000..d4850e1
--- /dev/null
+++ b/schema/topic.mod
@@ -0,0 +1,1899 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Display attributes is a parameter entity declaration in the topic DTD that includes
+attributes whose values may be used for affecting the display of a topic or its
+selection by search tools.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Relation attributes is a parameter entity declaration in the topic DTD that includes
+attributes whose values may be used for conditional processing or for selection by
+search tools.
+
+
+
+
+
+
+
+
+
+ ID attributes is a parameter entity declaration in the topic DTD that includes
+attributes whose values may be used for conditional processing or for selection by
+search tools.
+
+
+
+
+
+
+
+ Select attributes is a parameter entity declaration in the topic DTD that includes
+attributes whose values may be used for affecting the display of a topic or its
+selection by search tools.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Universal attributes is a parameter entity declaration in the topic DTD that
+includes all of the attributes in the select-atts and id-atts attribute groups.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Topic is the archetype from which other typed topics may be derived. Its body has completely optional content, which allows topic to be used as a titled container role: migration target for XHTML, other hierarchically structured source.
+
+This is the top-level DITA element for a single-subject topic or article. Other top-level DITA elements that are more content-specific are <concept>, <task>, and <reference>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a heading or label for the main parts of a document such as
+<topic>, <section>, and <example> and for the exhibit elements such as figure
+<fig> and <table>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a short description of a topic which indicates the content or
+intent of the topic more completely than the title. This element does not allow
+paragraphs; use <longdesc> if paragraphs are needed for a longer description. One
+possible use of this element is to provide a link preview or hover-help for links to
+this topic from other topics or documents.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This is the containing element for the main content of a <topic>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element is a division in a <topic>. Use sections for organizing subsets of
+information that are directly related to the topic. For example, Syntax, Usage, and
+Example might all be sections within a topic about a command-line process.
+Sections within a<topic> do not represent a hierarchy, but rather parallel divisions
+of that <topic> so they cannot be nested. If you want to accomplish nesting (for
+example, documenting options within a process each of which has its own syntax,
+usage and example), do so by creating subtopics insteads. Section <title>s are
+optional and should be used first in a section.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element is a section that has the specific role of containing examples that
+illustrate or support the current topic. <example> has the same content.model as
+<section>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains the description of a figure, table, object, or linkgroup. A
+8lt;desc> should provide more information than the title.
+
+
+
+
+ This could be trex, xpath, relax, xsd, etc.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The prolog contains information about the whole topic (for example, author
+information, subject category, and relationships to other topics) that is either
+entered by the author or machine-maintained. Much of the metadata will not be
+displayed with the topic on output, but may be used by processes generating
+search indexes, or customizing navigation.
+
+Links defined in the prolog are typically displayed as part of the topic on output,
+but their placement in the output will be dependent on the process, and is not
+directly controlled by the author.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The metadata section of the <prolog> contains information about a topic such as
+audience and product information. Metadata can be used by processes to select
+particular topics or to prepare search indexes or customize navigation.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element allows multiple links to be specified in a <prolog>. At processing
+time, they may be displayed elsewhere (for example, at the end of the topic). By
+relegating links to the prolog, it becomes easier to reuse the content of the topic in
+new collections or delivery contexts, where the related topics may not be available.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+ This element defines a hyperlink to another topic (either in the same file or a
+different file). If you leave the title empty, the text of the hyperlink will be derived
+from the title of the target. The link placement on output will depend on the type
+of the link and the logic of the output process. Often hyperlinks are displayed in a
+group at the end of the topic, even though they are defined in a topics prolog.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The <ph> element logically groups a set of words or phrase-level elements, for
+selection by property or formatting according to the typestyle attribute. Phrases
+can define containment structures to associate one element with another, such as
+associating a footnote with a specific sentence, or they can be used as a base for
+specialization to create specific kinds of phrases. When specializing, do not include
+the typestyle attribute: once you have identified a semantic class of information,
+you should associate formatting using a stylesheet. Storing formatting instructions
+in topic content limits the reusability of the information, and is only appropriate
+when authoring at a base level, where there aren't enough semantic elements for a
+stylesheet to operate on.
+
+The <ph> element can also be used to associate a specific property with a specific
+phrase. For example, you can associate a revision or version level with a phrase, or
+identify a word as a particular type of data for special processing.
+
+This element is also used during source migration when it is not apparent which
+new elements should be used for tagging.
+
+
+
+
+
+ var & keyword defined by syntax diagram
+
+
+
+
+
+
+
+
+
+
+
+
+ This element identifies a term that is specific to a particular vocabulary. It may be
+used to generate keyword links to a glossary, or to generate a glossary based on
+terms used in a particular collection of topics.
+
+
+
+
+
+ Inline content (prhases)
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Use this element to express yes or no values, or true or false
+values. The element itself is empty; you store the value of the element in
+its state attribute. This element is primarily for specialization, where it
+could be used to require a true | false choice in a particular part of the
+document. For example, a specialized application program interface (API) topic
+type could include an <abstractclass> element as a specialization of <boolean>,
+to allow authors to specify whether the interface being documented is abstract or
+concrete.
+
+
+
+
+
+
+
+
+
+
+
+
+ This empty element can specify a name/value pair. It is primarily
+intended for use by specializations, which can create specific kinds of state
+elements with fixed name values and a choice of values. For example, a specialized
+<accesstype> element could have a fixed name of "Access Type" (defined
+in a side file for translation purposes) and enumerated values of public,
+protected, and private.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A paragraph is a block of text containing a single main idea.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element indicates content quoted from another source. Use <q>
+for quotations that are too long for inline use. You can store a link to the
+source of the quotation in the href attribute.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A note contains information, differentiated from the main text, which
+expands on or calls attention to a particular point.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A quotation phrase indicates content quoted from another source.
+ This element is used inline; use <lq> for long quotations set off from
+the surrounding text.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This is an unordered list where the order of the list items is not
+significant.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ An ordered list is a list of items sorted by sequence or order of
+importance.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ An ordered list is a list of items sorted by sequence or order of
+importance.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A list item is a single item in an ordered <ol> or unordered <ul>
+list. Numbers and alpha characters are usually output with list items in ordered
+lists; bullets and dashes are usually output with list items in unordered
+lists.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element allows specialization in a list item. For example,
+if you want to create a new element that represents part of a list item (for
+example, an "additional information" section of a task step), you can specialize
+from lisection. In topic, lisection has no purpose other than to logically
+group content within a list item; it has no intended display characteristics.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A definition list is a list of terms and corresponding definitions.
+ The term (<dt>) is usually flush left. The description or definition
+(<dd>) is usually either indented and on the next line, or on the same
+line to the right of the term.You may also provide an optional heading
+for the terms and definitions, using the <dlhead> element, which contains
+header elements for those columns. The default formatting looks like a table
+with a heading row.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A <dlhead> contains optional headings for the term and description
+columns in a definition list. <dlhead> contains a heading <dthd> for
+the column of terms and an optional heading <ddhd> for the column of descriptions.
+The default formatting looks like a table with a heading row.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element can contain an optional heading or title for a column
+of descriptions or definitions in a definition list.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element is contained in a definition or description list head
+(<dlhead>) and provides an optional heading for the column of terms in
+a description list.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a single entry in a definition list that includes
+a term <dt> and one or more definitions or descriptions <dd> of that
+term.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains a term in a description (definition) list.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element contains the description of a term in a description/definition
+list.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This block element contains images or other displays or objects along
+with an optional title and description.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ More Information to be added
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A <pre> is a block element indicating text that has been formatted
+for the screen and is rendered using a fixed-width font. All whitespace,
+including multiple spaces, tabs, carriage returns and line feeds, is interpreted
+literally and retained in the display. Use this element for computer listings
+and program content.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Lines are like paragraphs (<p>), except that line endings are
+significant and are preserved.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This empty element specifies a non-text object such as an image,
+vector graphic, or video clip. This element includes an alternate text description
+<alt> that can be read as an alternative to viewing the object itself.
+Linking to a multi-media object is done by referencing the ID of the containing
+element, for example, <fig>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ describe new alt element here
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element corresponds to the HTML <object> element. <object>
+allows authors to include (embed) images, applets, plug-ins, ActiveX controls,
+video clips, and so on in a topic for rendering after transformation to HTML.
+(You can also use the <image> element for graphics.) The <object>
+element can contain attributes, a description, and parameters
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This empty element specifies a set of values that may be required
+by an <object> at run-time. Any number of <param> elements may appear
+in the content of an <object> in any order, but must be placed at the start
+of the content of the enclosing <object>. This element is comparable to
+the XHMTL <param> element. More information about <param> can be found
+at
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This is a container element for a simple table used to present
+information in unspanned columns and rows, when a CALS <table> is too complex.
+A simple table can be labeled either across the top or down a column, or both.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element indicates the top row of a semantic table and contains
+the column heads.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element specifies a row in a semantic table, like <row> in
+<table>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element in a simple table represents a table cell, like <entry>
+in a <table>.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element is specifically for containing discussions that are
+needed during the document review process. A reviewer can open an issue identifying
+himself with the reviewer attribute. Discussion of a review comment can be
+added using the <discussion> element, again with author identified using
+the reviewer attribute on <discussion>. Tracking and disposition of review
+comments can be handled with the <review-comment> attributes.
+
+It is recommended that output stylesheets (other than those specifically for
+review purposes) strip out remaining <draft-comment> elements prior to
+publication and create a log file containing them.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element is a place-holder element for migrated elements that
+cannot be appropriately tagged without writer intervention.
+
+It is recommended
+that output stylesheets other than those for review purposes strip out remaining
+<required-cleanup> elements prior to publication and create a log file
+containing them.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A footnote is used for indicating a source or including text that
+is not appropriate for inclusion in-line. This element generates a number
+by default or a character according to the callout attribute value. To refer
+to the same footnote again, use a <link> with the attribute type set to
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A reference to an abstract index entry in a lookup table used by
+the indexing process. The current index location will be added to the abstract
+index entry on output.
+
+
+
+
+
+
+
+
+
+
+
+ Use this element to refer to another document, book, or website that
+is not part of your collection of topics. The citation can reference the document
+directly (through an internal or external URL) or indirectly (through a reference
+to a bibliographic entry in the same or another topic).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A cross-reference is a link to another topic, a significant figure
+or table in another topic, or an external web site.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/topic.xsd b/schema/topic.xsd
new file mode 100644
index 0000000..70f15e5
--- /dev/null
+++ b/schema/topic.xsd
@@ -0,0 +1,51 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/topic_domains.mod b/schema/topic_domains.mod
new file mode 100644
index 0000000..5cc4434
--- /dev/null
+++ b/schema/topic_domains.mod
@@ -0,0 +1,97 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/schema/ui-domain.mod b/schema/ui-domain.mod
new file mode 100644
index 0000000..e3ee6d2
--- /dev/null
+++ b/schema/ui-domain.mod
@@ -0,0 +1,100 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/utilities-domain.mod b/schema/utilities-domain.mod
new file mode 100644
index 0000000..44e3485
--- /dev/null
+++ b/schema/utilities-domain.mod
@@ -0,0 +1,99 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/schema/xml.xsd b/schema/xml.xsd
new file mode 100644
index 0000000..dd2e9d1
--- /dev/null
+++ b/schema/xml.xsd
@@ -0,0 +1,97 @@
+
+
+
+
+
+
+ See http://www.w3.org/XML/1998/namespace.html and
+ http://www.w3.org/TR/REC-xml for information about this namespace.
+
+
+
+
+ This schema defines attributes and an attribute group
+ suitable for use by
+ schemas wishing to allow xml:base, xml:lang or xml:space attributes
+ on elements they define.
+
+ To enable this, such a schema must import this schema
+ for the XML namespace, e.g. as follows:
+ <schema . . .>
+ . . .
+ <import namespace="http://www.w3.org/XML/1998/namespace"
+ schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>
+
+ Subsequently, qualified reference to any of the attributes
+ or the group defined below will have the desired effect, e.g.
+
+ <type . . .>
+ . . .
+ <attributeGroup ref="xml:specialAttrs"/>
+
+ will define a type which will schema-validate an instance
+ element with any of those attributes
+
+
+
+
+ In keeping with the XML Schema WG's standard versioning
+ policy, this schema document will persist at
+ http://www.w3.org/2001/03/xml.xsd.
+ At the date of issue it can also be found at
+ http://www.w3.org/2001/xml.xsd.
+ The schema document at that URI may however change in the future,
+ in order to remain compatible with the latest version of XML Schema
+ itself. In other words, if the XML Schema namespace changes, the version
+ of this document at
+ http://www.w3.org/2001/xml.xsd will change
+ accordingly; the version at
+ http://www.w3.org/2001/03/xml.xsd will not change.
+
+
+
+
+
+ In due course, we should install the relevant ISO 2- and 3-letter
+ codes as the enumerated possible values . . .
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ See http://www.w3.org/TR/xmlbase/ for
+ information about this attribute.
+
+
+
+
+
+
+
+
+
+