This indicates tothe document processing system that there may be "ArcBase" processing instructions in the SMDL meta-DTD that will specify the base architectures from which SMDL is derived.

NOTE 10
In effect, this is an invocation of the "Base Architecture" identification facility found in Annex C of the HyTime International Standard. It does not invoke the HyTime architecture.

6.2 Identification of Base Architecture

The SMDL meta-DTD indicates the fact that its architecture is derived from the HyTime base architecture by means of an ArcBase processing instruction. In SGML's reference concrete syntax, it would appearas follows:

This processing instruction establishes that HyTime is the SMDL meta-DTD's local name for one of its base architectures, and that aftert his processing instruction, the document processing system can expect to find:

• a) An SGML NOTATION declaration that identifies the architecture definition document (in this case, the HyTime International Standard). Associated with this NOTATION declaration must be an attribute definition list (an ATTLIST) that declares the support attributes of the architecture. The HyTime International Standard itself defines these attributes, but this attribute definition list must also appear in e very meta-DTD derived from HyTime. The list therefore forms a part of the SMDL meta-DTD, and it appears below using SGML's reference concrete syntax.

• b) an SGML general ENTITY declaration that identifies the meta-DTD of the base architecture (HyTime), and which may specify values for HyTime' s architectural support attributes.

6.2.1 Declaration of Base Architecture

The following SGML NOTATION declaration points to the HyTime International Standard. The ATTLIST that follows it defines the attribute list of the HyTime notation. These declarations have been copied here from the HyTime International Standard.

<!--HyTime Support Declarations -->

<!NOTATION HyTime PUBLIC "ISO/IEC 10744:1992//NOTATION

HyTime Architecture Definition Document//EN"

--A document architecture conforming to the

Architectural Form Definition Requirements of

International Standard ISO/IEC 10744. --

>

<!ATTLIST #NOTATION HyTime

--Support attributes for all architectures --

ArcFormA

--Attribute name: architectural form --

NAME #FIXED HyTime

ArcNamrA

--Attribute name: attribute renamer --

NAME #FIXED HyNames

ArcBridA

--Attribute name: bridge functions --

NAME #FIXED HyBrid

ArcDocF

--Architectural form name: documentelement --

NAME #FIXED HyDoc

ArcVer

--Architecture version identifier --

CDATA #FIXED "ISO/IEC 10744:1992"

--DerArc attributes --

--(Support attributes for derived architectures.) --

ArcCopy

--Forms copied from base architecture --

NAMES #IMPLIED ArcAlias

--Aliases fornames of copied forms. Constraint:

base name precedes alias. lextype(NAMES). --

NAMES #IMPLIED

--Support attributes for HyTime only --

hyqcnt

--Highest quantum count ceiling. Constraint: power

of 2 >= 32 (i.e., minimum value is 32). --

NUMBER #REQUIRED

base

--Base module. lextype(NMTOKENS) --

CDATA "" --Default: no options --

measure

--Measurement module. lextype(NMTOKENS). --

CDATA #IMPLIED --Default: no support --

locs

--Location address module. lextype(NMTOKENS). --

CDATA #IMPLIED --Default: no support --

links

--Hyperlinks module. lextype(NMTOKENS) --

CDATA #IMPLIED --Default: no support --

sched

--Scheduling module. lextype(NMTOKENS) --

CDATA #IMPLIED --Default: no support --

rend

--Rendition module. lextype(NMTOKENS) --

CDATA #IMPLIED --Default: no support --

>

NOTE 11
The above declarations appear verbatim in this official version of the SMDL meta-DTD. However, in a version of the SMDL meta-DTD used in the context of a particular application, these declarations could conceivably be go verned by an SGML declaration that defines a concrete syntax otherthan SGML's Reference Concrete Syntax. In such a case, they might not look exactly like the abo ve declarations, but they would have the same effect.

6.2.2 Declaration Template for the HyTime Meta-DTD Entity

The following SGML ENTITY declaration points to a file (here named "myhytime.mtd") containing those formalized SGML aspects of the HyTime International Standard (i.e., those portions of the HyTime meta-DTD), which are actually in effect for this application. An ENTITY declaration ha ving the same ef-fect as this one m ust appearin every SMDL meta-DTD document.

<!ENTITY HyTime --THIS ENTITY IS NOT TO BE REFERENCED! --

SYSTEM "myhytime.mtd" CDATA HyTime

[

hyqcnt=32

base=

"activity context dcnatts desctxt dvlistexidrefs HyLex HyPD lexord lextype refctl unparsed xpropdef"

measure=

"axismdu dimref fcsmdu homogran HyFunk HyOp markfun"

locs=

"anydtd anysgml uassert bigmatch coordlochyQ mixcase mixspace multloc notsrc pathloc query relloc spanloc"

links=

manyanch

sched=

"accanch calspec exrecon grpdex juldate manyaxes splitfcs"

rend=

"modify patch profun project scaleref"

ArcCopy=

"abstime accanch acclink acctype activity axis baton batrule bibloc calspec dataloc date descdef desctab desctxt dimlist dimref dimspec dvlisteventevgrp evsched exrecon extent extlist fcs fcsloc granule ilink juldate listloc mallobj markfun marklist modpatch modrule modscope mrkquery nameloc nmlist nmquery notloc pathloc profun projectr proploc proscope relloc rendrule scaleref timeoff treeloc wand wandrule wndpatch"

ArcAlias=

" HyDoc work

fcs cantus

evsched thread

evsched lyric

evgrp tuplet

event pitched

event rest

ilink perform

ilink score

ilink analysis"

]>

[ Index | Previous Paragraph | Next Paragraph ]