XML Source of "conceptMod.xsd"
See Also: |
|
Schema Location: |
http://docs.oasis-open.org/dita/v1.1/OS/schema/conceptMod.xsd |
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<!-- ============================================================= -->
<!-- HEADER -->
<!-- ============================================================= -->
<!-- MODULE: DITA Concept XSD Module -->
<!-- VERSION: 1.1 -->
<!-- DATE: November 2006 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Darwin Information Typing Architecture (DITA) -->
<!-- -->
<!-- PURPOSE: W3C XML Schema to describe DITA concepts -->
<!-- -->
<!-- ORIGINAL CREATION DATE: -->
<!-- March 2001 -->
<!-- -->
<!-- (C) Copyright OASIS-Open.org 2005, 2006 -->
<!-- (C) Copyright IBM Corporation 2001, 2004. -->
<!-- All Rights Reserved. -->
<!-- ============================================================= -->
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<!-- ==================== Import Section ======================= -->
<!--Embed concept to get specific elements -->
<xs:annotation>
<xs:documentation>
The <
<keyword>concept</keyword>
> element is the top-level
element for a topic that answers the question
<q>what is?</q>
Concepts provide
background information that users must know before they can successfully work
with a product or interface. Often, a concept is an extended definition of
a major abstraction such as a process or function. It might also have an example
or a graphic, but generally the structure of a concept is fairly simple.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="concept.class">
<xs:attribute default="- topic/topic concept/concept " ref="class"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:annotation>
<xs:documentation>
The <
<keyword>conbody</keyword>
> element is the main body-level
element for a concept. Like the body element of a general topic, <
<keyword>conbody</keyword>
>
allows paragraphs, lists, and other elements as well as sections and examples.
But <
<keyword>conbody</keyword>
> has a constraint that a section
or an example can be followed only by other sections or examples.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="conbody.class">
<xs:attribute default="- topic/body concept/conbody " ref="class"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
</xs:group>
<!-- Base type: topic.class -->
<xs:sequence>
<xs:group ref="title"/>
<xs:choice minOccurs="0">
</xs:choice>
<xs:group minOccurs="0" ref="prolog"/>
<xs:group minOccurs="0" ref="conbody"/>
</xs:sequence>
<xs:attribute name="id" type="xs:ID" use="required"/>
<xs:attribute name="conref" type="xs:string"/>
</xs:complexType>
<!-- Base type: body.class -->
<xs:sequence>
<xs:group maxOccurs="unbounded" minOccurs="0" ref="body.cnt"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
</xs:choice>
</xs:sequence>
<xs:attribute name="base" type="xs:string"/>
</xs:complexType>
</xs:schema>