[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

XSchema Specification - Extensions (Section 2.6), Draft 3

• From: "Simon St.Laurent" <SimonStL@c...>
• To: "Xml-Dev (E-mail)" <xml-dev@i...>
• Date: Tue, 18 Aug 98 23:43:15 UT

The latest draft for the XSC:Doc and XSC:More elements follows, updated for 
namespaces. Because these elements may (or must, in the case of XSC:Doc) 
contain elements that use other namespaces, the rules are slightly different.

As always, a prettier HTML version of this will be posted shortly at 
http://purl.oclc.org/NET/xschema. 

Simon St.Laurent
Dynamic HTML: A Primer / XML: A Primer / Cookies

2.6 XSchema Extensions

XSchema provides areas in which XSchema developers can provide supplemental 
information and metadata regarding XSchema components in both human- and 
machine-readable formats. Human-readable information is provided through the 
use of a subset of HTML that conforms to XML syntax, while machine-readable 
information may be provided through the XSC:More element.

2.6.1 Documentation Extensions

Human-readable documentation for XSchemas should be provided using the Itsy 
Bitsy Teeny Weeny Simple Hypertext (IBTWSH) format created by John Cowan. The 
full DTD is available at http://www.ccil.org/~cowan/XML/ibtwsh.dtd. 
Documentation that uses portions of the IBTWSH format may be included in the 
XSC:Doc element, a subelement available to all declarations. The XSC:Doc 
element provides basic formatting options for XSchema documentation.

<!ENTITY % ibtwsh SYSTEM "http://www.ccil.org/~cowan/XML/ibtwsh.dtd">
%ibtwsh;
<!ELEMENT XSC:Doc %horiz.model;>
<!ATTLIST XSC:Doc
    xmlns CDATA #FIXED "">

Note that because XSC:Doc redefines the default namespace to support IBTWSH, 
the XSC: prefix must be used for XSC:Doc.  Any element allowed in the IBTWSH 
horiz.model set of elements (A, BR, SPAN, XML, CITE, CODE, DFN, EM, KBD, SAMP, 
STRONG, VAR, or parsed character data) may be used in the XSC:Doc element. 
Note that IBTWSH does not use namespaces in order to preserve compatibility 
with HTML.
XSchema applications should ignore all XSchema declarations (i.e., elements 
prefixed with XSC: or another appropriate XSchema prefix) within an XSC:Doc 
element. (The XML element of IBTWSH allows an ANY content model.)

2.6.2 Other Extensions

The XSC:More element provides an area which developers can use to create their 
own supplements to XSchema, defining content types more tightly than is 
possible through XSchema 1.0. The XSC: More element has a simple ANY content 
model, though XSchema processors should ignore the appearance of any elements 
from the XSchema namespace in this area.

<!ELEMENT XSC:More ANY>
<!ATTLIST XSC:More
    xmlns CDATA "">

Because XSC:More redefines the default namespace, the XSC: prefix must be used 
for XSC:More.  Developers may override the blank value of the xmlns attribute 
to define their own default namespace for elements contained in the XSC:More 
element.


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Re: Is XML getting too hard?
• Next by Date: XSchema Spec - Attribute Declarations (Section 2.4), Draft 6
• Previous by thread: Re: Is XML getting too hard?
• Next by thread: XSchema Spec - Attribute Declarations (Section 2.4), Draft 6
• Index(es):
  • Date
  • Thread