% \iffalse meta-comment
%
% Author: Peter Wilson (CUA and NIST)
% 
%  This system is distributed in the hope that it will be useful,
%  but WITHOUT ANY WARRANTY; without even the implied warranty of
%  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
% 
% \fi
% \CheckSum{1344}
%% \CharacterTable
%%  {Upper-case    \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
%%   Lower-case    \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
%%   Digits        \0\1\2\3\4\5\6\7\8\9
%%   Exclamation   \!     Double quote  \"     Hash (number) \#
%%   Dollar        \$     Percent       \%     Ampersand     \&
%%   Acute accent  \'     Left paren    \(     Right paren   \)
%%   Asterisk      \*     Plus          \+     Comma         \,
%%   Minus         \-     Point         \.     Solidus       \/
%%   Colon         \:     Semicolon     \;     Less than     \<
%%   Equals        \=     Greater than  \>     Question mark \?
%%   Commercial at \@     Left bracket  \[     Backslash     \\
%%   Right bracket \]     Circumflex    \^     Underscore    \_
%%   Grave accent  \`     Left brace    \{     Vertical bar  \|
%%   Right brace   \}     Tilde         \~}
%
% \def\fileversion{v1.0}
% \def\filedate{1996/05/31}
% \title{Package files for ISO Standard 10303 for 
%        \LaTeX{} version 2e\thanks{This
%        file has version number \fileversion, last revised
%        \filedate.}}
%
% \author{%
% Peter Wilson\\
% Catholic University of America and NIST \\
% {\tt pwilson@cme.nist.gov}
% }
% \date{\filedate}
% \maketitle
% \tableofcontents
%
% \StopEventually{}
%
% \section{Introduction}
%
% These package files are intended for the typesetting of documents
% according to the rules for ISO international standards,
% and specifically for the ISO~10303 standard commonly
% referred to as `STEP'.
%
% Document layout is according to the specifications in
% ISO Directives~\cite{ISODIR}. Unfortunately these Directives do not
% completely define the document layout, leaving several
% aspects open to interpretation by the document editor
% and re-interpretation by the ISO editorial board.
% In the case of STEP an additional set of informal
% `Supplementary Directives' have been established by the ISO TC184/SC4
% Editing Committe~\cite{SD}. The packages defined herein meet
% the requirements of both of these Directives.
%
% The STEP standard has been published by ISO from camera ready
% copy derived from electronic sources (this also means that ISO
% has not objected to the typographical conventions supported
% by these packages). Within ISO there are moves
% afoot to publish directly from SGML tagged electronic sources.
% The packages have been designed to simplify the conversion from
% \LaTeX\ to SGML tagging. Thus, there are more document structural
% elements defined than is usual with \LaTeX.
% 
% \section{The {\sc docstrip} modules}
%
% The following modules are used in the implementation to direct
% {\sc docstrip} in generating the external files:
% \begin{center}
% \begin{tabular}{ll}
%   step    & produce the package/style step\\
%   ir      & produce the package/style ir \\
%   ap      & produce the package/style ap\\
%   ats     & produce the package/style ats\\
%   aic     & produce the package/style aic\\
%   fwd2    & produce boilerplate file stpptlst.tex \\
%   fwd3    & produce boilerplate file stpdvlst.tex \\
%   apf1    & produce boilerplate file apendint.tex \\
%   apf2    & produce boilerplate file apmptbl.tex \\
%   atsf1   & produce boilerplate file tsendint.tex \\
%   atsf2   & produce boilerplate file atsprpbp.tex \\
%   driver  & produce a documentation driver file \\
% \end{tabular}
% \end{center}
%
% \subsection{A driver for this document}
%
% The next bit of code contains the documentation driver file for
% \TeX{}, i.e., the file that will produce the documentation you are
% currently reading. It will be extracted from this file by the 
% {\sc docstrip} program.
%
%    \begin{macrocode}
%<*driver>
\documentclass{ltxdoc}
%    \end{macrocode}
%
%    We do want an index, using linenumbers, and update information
%    \begin{macrocode}
\EnableCrossrefs
\CodelineIndex
\RecordChanges
%    \end{macrocode}
%    We use so many \file{docstrip} modules that we set the
%    \texttt{StandardModuleDepth} counter to 1.
%    \begin{macrocode}
\setcounter{StandardModuleDepth}{1}
%    \end{macrocode}
%    Some commonly used abbreviations
%    \begin{macrocode}
\newcommand*{\Lopt}[1]{\textsf {#1}}
\newcommand*{\file}[1]{\texttt {#1}}
\newcommand*{\Lcount}[1]{\textsl {\small#1}}
\newcommand*{\pstyle}[1]{\textsl {#1}}
%    \end{macrocode}
%    We also want the full details.
%    \begin{macrocode}
\begin{document}
\DocInput{stepe.dtx}
\PrintIndex
\PrintChanges
\end{document}
%</driver>
%    \end{macrocode}
%
% \section{Identification}
%
%    These packages may be used with either \LaTeXe\ or \LaTeX 209.
%    We use a flag to avoid \LaTeXe\ code being processed by
%    \LaTeX 209.
%    \begin{macrocode}
%<*step|ir|ap|ats|aic>
\@ifundefined{ProvidesPackage}{%
%    \end{macrocode}
%
%    Announce the Package name and its version:
%    \begin{macrocode}
%<*step>
\typeout{stepv1.sty [1996/05/31 STEP general style]}}{%
\ProvidesPackage{stepv1}[1996/05/31 STEP general package]}
%</step>
%<*ir>
\typeout{irv1.sty [1996/05/31 STEP IR style]}}{%
\ProvidesPackage{irv1}[1996/05/31 STEP IR package]}
%</ir>
%<*ap>    
\typeout{apv1.sty [1996/05/31 STEP AP style]}}{%
\ProvidesPackage{apv1}[1996/05/31 STEP AP package]}
%</ap>
%<*ats>   
\typeout{atsv1.sty [1996/05/31 STEP ATS style]}}{%
\ProvidesPackage{atsv1}[1996/05/31 STEP ATS package]}
%</ats>
%<*aic>   
\typeout{aicv1.sty [1996/05/31 STEP AIC style]}}{%
\ProvidesPackage{aicv1}[1996/05/31 STEP AIC package]}
%</aic>
%</step|ir|ap|ats|aic>
%    \end{macrocode}
%
%    Now the identification of the boilerplate text files.
%    \begin{macrocode}
%<fwd2>\typeout{stpptlst.tex [1996/05/31 STEP forward parts list]}
%<fwd3>\typeout{stpdvlst.tex [1996/05/31 STEP forward divisions list]}
%<apf1>\typeout{apendint.tex [1996/05/31 STEP AP end intro boilerplate]}
%<apf2>\typeout{apmptbl.tex [1996/05/31 STEP AP mapping table boilerplate]}
%    \end{macrocode}
%
%    The \file{stepv1} package is the main documentation style for
%    STEP. Some of the other packages require this to be loaded.
%    \begin{macrocode}
%<*ir|ap|ats|aic>
\@ifundefined{RequirePackage}{}{%
    \RequirePackage{stepv1}[1995/05/31]
}
%</ir|ap|ats|aic>
%    \end{macrocode}
%
% \section{Initial Code}
%
%    In this part we define a few commands that are used later on.
%
% \begin{macro}{\stepemptystring}
%    This is an alias for the |\isoemptystring| command (for
%    the purposes of upwards compatibility).
%    We use in in testing for an empty parameter.
%    \begin{macrocode}
%<step> \let\stepemptystring\isoemptystring
%    \end{macrocode}
% \end{macro}
%
% \section{The STEP package}
%
%    This section defines the facilities available in the STEP package.
%    \begin{macrocode}
%<*step>
%    \end{macrocode}
%
% \subsection{Preamble commands}
%
%    The commands defined in this section should, if required,
%    be placed in the document preamble.
%
% \begin{macro}{\partno}
% \begin{macro}{\thespartno}
%    |\partno{|\meta{part number}|}| specifies the part number 
%    for ISO 10303. Internally, it is referred to by |\thespartno|.
%    \begin{macrocode}
\gdef\thespartno{}
\newcommand{\partno}[1]{\gdef\thespartno{#1}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \subsection{Indexing style commands}
%
%    We make sure that the index style commands are appropriate.
%
% \begin{macro}{\indexfill}
% \begin{macro}{\sindexfill}
% \begin{macro}{\ssindexfill}
%    Dotted lines between an index entry and the page number.
%    \begin{macrocode}
\renewcommand{\indexfill}{\dotfill}
\renewcommand{\sindexfill}{\dotfill}
\renewcommand{\ssindexfill}{\dotfill}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\alphaindexspace}
% \begin{macro}{\otherindexspace}
%    No extra vertical spacing between blocks of index entries,
%    \begin{macrocode}
\renewcommand{\alphaindexspace}[1]{}
\renewcommand{\otherindexspace}[1]{}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\indexsee}
% \begin{macro}{\indexseealso}
%    Formatting of {\em see} and {\em see also}.
%    \begin{macrocode}
\renewcommand{\indexsee}[1]{\par \hspace*{2em} {\em see} #1}
\renewcommand{\indexseealso}[1]{\par \hspace*{2em} {\em see also} #1}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\ix}
%    Both print and index a word or phrase.
%    \begin{macrocode}
\newcommand{\ix}[1]{#1\index{#1}}
%    \end{macrocode}
% \end{macro}
%
% \subsection{Miscellaneous commands}
%
% \subsubsection{Font changes}
%
% \begin{macro}{\B}
% \begin{macro}{\E}
% \begin{macro}{\BG}
%    |\B{|\meta{text}|}| prints \meta{text} in bold while |\E{|\meta{text}|}|
%    prints it {\em emphasized}. |\BG{|\meta{mathsymbol}|}| prints
%    \meta{mathsymbol} in bold.
%    \begin{macrocode}
\newcommand{\B}[1]{{\bf #1}}
\newcommand{\E}[1]{{\em #1}}
\newcommand{\BG}[1]{{\mbox{\boldmath $#1$}}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \subsubsection{Logos}
%
% \begin{macro}{\Express}
% \begin{macro}{\ExpressG}
% \begin{macro}{\ExpressI}
%    The commands print the logos for the {\small\sc EXPRESS} family
%    of information modeling languages.
%    \begin{macrocode}
\newcommand{\Express}{{\small\sl EX\-PRESS}}
\newcommand{\ExpressG}{{\small\sl EX\-PRESS-G}}
\newcommand{\ExpressI}{{\small\sl EX\-PRESS-I}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \subsubsection{EXPRESS code symbols}
%
% \begin{macro}{\nexp}
%    Highlight an EXPRESS-defined name.
%    \begin{macrocode}
\newcommand{\nexp}[1]{{\bf #1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\HASH}
% \begin{macro}{\LT}
% \begin{macro}{\LE}
% \begin{macro}{\NE}
% \begin{macro}{\INE}
% \begin{macro}{\GE}
% \begin{macro}{\GT}
% \begin{macro}{\CAT}
% \begin{macro}{\HAT}
% \begin{macro}{\QUES}
% \begin{macro}{\BS}
% \begin{macro}{\IEQ}
% \begin{macro}{\INEQ}
%    Various symbols used within EXPRESS.
%    \begin{macrocode}
\newcommand{\HASH}{{\small\tt \#}}
\newcommand{\LT}{{\small\tt <}}
\newcommand{\LE}{{\small\tt <=}}
\newcommand{\NE}{{\small\tt <>}}
\newcommand{\INE}{{\small\tt :<>:}}
\newcommand{\GE}{{\small\tt >=}}
\newcommand{\GT}{{\small\tt >}}
\newcommand{\CAT}{{\small\tt ||}}
\newcommand{\HAT}{{\small\tt ^}}
\newcommand{\QUES}{{\small\tt ?}}
\newcommand{\BS}{{\small\tt \\}}
\newcommand{\IEQ}{{\small\tt :=:}}
\newcommand{\INEQ}{{\small\tt :<>:}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
%
%
% \subsubsection{marginal notes}
%
% \begin{macro}{\mnote}
%    Put a note into the document margin. This is only operative when
%    the \Lopt{draft} option is in effect.
%    
%    \begin{macrocode}
\newcommand{\mnote}[1]{\ifdr@ftd@c
                         \marginpar{\raggedright\tiny #1}
                       \fi}
%    \end{macrocode}
% \end{macro}
%
% \subsection{EXPRESS code documentation environments}
%
%    The commands and environments in this section are for documenting
%    EXPRESS code.
%
% \begin{environment}{specific@tion}
%    An environment to tag the body of a specification.
%    \begin{macrocode}
\newenvironment{specific@tion}[1]{}{}
%    \end{macrocode}
% \end{environment}
% 
% \begin{environment}{espec}
% \begin{environment}{fspec}
% \begin{environment}{rspec}
% \begin{environment}{tspec}
%    Environments for tagging the bodies of entity, function, rule and
%    type specifications.
%    \begin{macrocode}
\newenvironment{espec}[1]{}{}
\newenvironment{fspec}[1]{}{}
\newenvironment{rspec}[1]{}{}
\newenvironment{tspec}[1]{}{}
%    \end{macrocode}
% \end{environment}
% \end{environment}
% \end{environment}
% \end{environment}
%
% \begin{environment}{dtext}
%    An environment to tag descriptive text.
%    \begin{macrocode}
\newenvironment{dtext}{}{}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{ecode}
%    Environment for writing EXPRESS code.
%    \begin{macrocode}
\newenvironment{ecode}{\par\noindent 
    \protect\underline{\Express\ specification}:
    \begin{Efont}}%
    {\end{Efont}}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{expdesc}
%     A non-indented description environment.
% \begin{macro}{\expdesclabel}
%    The label for the description list. Note that it includes a colon.
%    \begin{macrocode}
\newcommand{\expdesclabel}[1]{{\bf #1:}}
%    \end{macrocode}
% \end{macro}
%
%    \begin{macrocode}
\newenvironment{expdesc}{\list{}%
    {\leftmargin 0pt \labelsep 0.5em
     \itemindent 0.5em \labelwidth\z@
     \let\makelabel\expdesclabel}}%
    {\endlist}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{attrlist}
%     Listing of attribute descriptions.
%    \begin{macrocode}
\newenvironment{attrlist}{\par\noindent
    \protect\underline{Attribute definitions}:
    \begin{expdesc}}%
    {\end{expdesc}}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{fproplist}
%    Listing of formal propositions.
%    \begin{macrocode}
\newenvironment{fproplist}{\par\noindent
    \protect\underline{Formal propositions}:
    \begin{expdesc}}%
    {\end{expdesc}}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{iproplist}
%    Listing of informal propositions.
%    \begin{macrocode}
\newenvironment{iproplist}{\par\noindent
    \protect\underline{Informal propositions}:
    \begin{expdesc}}%
    {\end{expdesc}}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{enumlist}
%    Listing of enumerated items.
%    \begin{macrocode}
\newenvironment{enumlist}{\par\noindent
    \protect\underline{Enumerated item definitions}:
    \begin{expdesc}}%
    {\end{expdesc}}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{arglist}
%    Listing of argument definitions.
%    \begin{macrocode}
\newenvironment{arglist}{\par\noindent
    \protect\underline{Argument definitions}:
    \begin{expdesc}}%
    {\end{expdesc}}
%    \end{macrocode}
% \end{environment}
%
% \subsection{STEP part title}
%
% \begin{macro}{\stepparttitle}
%    A special title command for STEP parts. \\
%    |\stepparttitle{|\meta{Part title}|}| \\
%    It is implemented in the same manner as the general ISO |\title|
%    command but using specific title wording.
%    \begin{macrocode}
\gdef\thestepparttitle{}
\newcommand{\scivm@in}{Industrial automation systems and integration ---\\}
\newcommand{\stepc@mp}{Product data representation and exchange ---\\}
\newcommand{\thisp@rtno}[1]{Part #1 :\\}
\newcommand{\sptitle}[1]{#1}
\newcommand{\stepparttitle}[1]{%
    \clearpage\pagenumbering{arabic}
    \setcounter{section}{0}
    \setcounter{clause}{0}
    \if@therd@c \else 
        \protect\thispagestyle{isotitlehead}
    \fi
    \gdef\thestepparttitle{{\Tfont\bf \scivm@in \stepc@mp 
                             \thisp@rtno{\thespartno} \sptitle{#1}}}
    \if@twocolumn
       \twocolumn[\vbox to 35mm{\thestepparttitle}]
    \else
        \vbox to 35mm{\thestepparttitle}
    \fi}
%    \end{macrocode}
% \end{macro}
%
% \subsection{Headings and boilerplate}
%
%    There are certain elements within a standard that are predetermined.
%
% \subsubsection{Foreword elements}
%
% \begin{macro}{\Foreword}
%    This command introduces the Foreword for ISO~10303.
%
% \changes{v1}{1995/05/31}{Deleted `contributions from Foreword.}
% \changes{v1}{1995/05/31}{SC4 has changed its name to Industrial Data.}
%    \begin{macrocode}
\newcommand{\Foreword}{%
    \begin{foreword}
    \input{isofwdbp}

    International Standard ISO~10303--\thespartno\ was 
    prepared by Technical Committee
    ISO/TC~184, {\em Industrial automation systems and integration,}
    Subcommittee SC4, {\em Industrial data.}
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\endForeword}
%    The command for ending the STEP Foreword. Use as: \\
%    |\endForeword{|\meta{normannexes}|}{|\meta{infannexes}|}|
%    \begin{macrocode}
\gdef\endForeword#1#2{%
      ISO~10303 consists of the following parts under the general title
      {\em Industrial automation systems and integration -- Product data
      representation and exchange:}
      \fwdpartslist

    The structure of this International Standard is described in ISO~10303-1.
The numbering of the parts of this International Standard reflects
its structure:
\fwddivslist
Should further parts of ISO~10303 be published, they will follow the 
same numbering pattern.

% Don't talk about annexes if relevent argument is empty. 
\if\stepemptystring{#1} \else%
#1 an integral part of this part of ISO~10303. \fi%
\if\stepemptystring{#2} \else%
#2 for information only. \fi
\end{foreword}
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\fwdpartslist}
% \begin{macro}{\fwddivslist}
%    These commands typeset the list of STEP parts and the list of STEP
%    documentation divisions, respectively.
%    \begin{macrocode}
\newcommand{\fwdpartslist}{\input{stpptlst}}
\newcommand{\fwddivslist}{\input{stpdvlst}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
%    The following is the contents of the file \file{stpptlst.tex}. It consists
%    of the current STEP parts.
%    \begin{macrocode}
%</step>
%<*fwd2>
  %%%% stpptlst.tex  STEP part listing.
%
\begin{itemize}
\item Part 1, Overview and fundamental principles;
\item Part 11, Description method: EXPRESS language reference
   manual;
\item Part 12, Description method: EXPRESS-I language reference
   manual;
\item Part 13, Description method: Architecture and methodology
   reference manual;
\item Part 21, Implementation method: Clear text encoding of the
   exchange structure;
\item Part 22, Implementation method: Standard data access interface
   specification;
\item Part 23, Implementation method: C++ language binding to the
   standard data access interface;
\item Part 24, Implementation method: C language binding to the
   standard data access interface;
\item Part 26, Implementation method: Interface definition language
   binding to the standard data access interface;
\item Part 31, Conformance testing methodology and framework:
   General concepts;
\item Part 32, Conformance testing methodology and framework:
   Requirements on testing laboratories and clients;
\item Part 33, Conformance testing methodology and framework:
   Structure and use of abstract test suites;
\item Part 34, Conformance testing methodology and framework:
   Abstract test methods;
\item Part 35, Conformance testing methodology and framework: 
   Abstract test methods for SDAI implementations;
\item Part 41, Integrated generic resource: Fundamentals of product
     description and support;
\item Part 42, Integrated generic resource: Geometric and
   topological representation;
\item Part 43, Integrated generic resource: Representation
   structures;
\item Part 44, Integrated generic resource: Product structure
   configuration;
\item Part 45, Integrated generic resource: Materials;
\item Part 46, Integrated generic resource: Visual presentation;
\item Part 47, Integrated generic resource: Shape variation
   tolerances;
\item Part 49, Integrated generic resource: Process structure and
   properties;
\item Part 101, Integrated application resource: Draughting;
\item Part 102, Integrated application resource: Ship structures;
\item Part 104, Integrated application resource: Finite element
   analysis;
\item Part 105, Integrated application resource: Kinematics;
\item Part 106, Integrated application resource: Building
   construction core model;
\item Part 201, Application protocol: Explicit draughting;
\item Part 202, Application protocol: Associative draughting;
\item Part 203, Application protocol: Configuration controlled
   design;
\item Part 204, Application protocol: Mechanical design using
   boundary representation;
\item Part 205, Application protocol: Mechanical design using
   surface representation;
\item Part 207, Application protocol: Sheet metal die planning and
   design;
\item Part 208, Application protocol: Life cycle management - Change
   process;
\item Part 209, Application protocol: Composite and metallic
   structural analysis and related design;
\item Part 210, Application protocol: Design of layered electronic
   products;
\item Part 211, Application protocol: Electronics test diagnostics
   and remanufacture;
\item Part 212, Application protocol: Electrotechnical design and
   installation
\item Part 213, Application protocol: Numerical control process
   plans for machined parts;
\item Part 214, Application protocol: Core data for automotive
   design processes;
\item Part 215, Application protocol: Ship arrangement;
\item Part 216, Application protocol: Ship moulded forms;
\item Part 217, Application protocol: Ship piping;
\item Part 218, Application protocol: Ship structures;
\item Part 220, Application protocol: Process planning, manufacture,
   and assembly of layered electronic products;
\item Part 221, Application protocol: Functional data and their
   schematic representation for process plant;
\item Part 222, Application protocol: Exchange of product data for
   composite structures;
\item Part 223, Application protocol: Exchange of design and
   manufacturing product information for cast parts;
\item Part 224, Application protocol: Mechanical product definition
   for process plans using mechanical feature; 
\item Part 225, Application protocol: Building elements using
   explicit shape representation;
\item Part 226, Application protocol: Ship mechanical systems;
\item Part 227, Application protocol: Plant spatial configuration;
\item Part 228, Application protocol: Building services: Heating,
   ventilation, and air conditioning;
\item Part 229, Application protocol: Exchange of design and
   manufacturing product information for forged parts;
\item Part 230, Application protocol: Building structural frame:
   Steelwork;
\item Part 231, Application protocol: Process engineering data:
   Process design and process specification of major equipment;
\item Part 301, Abstract test suite: Explicit draughting;
\item Part 302, Abstract test suite: Associative draughting;
\item Part 303, Abstract test suite: Configuration controlled
   design;
\item Part 304, Abstract test suite: Mechanical design using
   boundary representation;
\item Part 305, Abstract test suite: Mechanical design using surface
   representation;
\item Part 307, Abstract test suite: Sheet metal die planning and
   design;
\item Part 308, Abstract test suite: Life cycle management - Change
   process;
\item Part 309, Abstract test suite: Composite and metallic
   structural analysis and related design;
\item Part 310, Abstract test suite: Design of layered electronic
   products;
\item Part 311, Abstract test suite: Electronics test diagnostics
   and remanufacture;
\item Part 312, Abstract test suite: Electrotechnical design and
   installation;
\item Part 313, Abstract test suite: Numerical control process plans
   for machined parts;
\item Part 314, Abstract test suite: Core data for automotive
   mechanical design processes;
\item Part 315, Abstract test suite: Ship arrangement;
\item Part 316, Abstract test suite: Ship moulded forms;
\item Part 317, Abstract test suite: Ship piping;
\item Part 318, Abstract test suite: Ship structures;
\item Part 320, Abstract test suite: Process planning, manufacture,
   and assembly of layered electronic products;
\item Part 321, Abstract test suite: Functional data and their
   schematic representation for process plant;
\item Part 322, Abstract test suite: Exchange of product data for
   composite structures;
\item Part 323, Abstract test suite: Exchange of design and
   manufacturing product information for cast parts;
\item Part 324, Abstract test suite: Mechanical product definition
   for process plans using mechanical features;
\item Part 325, Abstract test suite: Building elements using
   explicit shape representation;
\item Part 326, Abstract test suite: Ship mechanical systems;
\item Part 327, Abstract test suite: Plant spatial configuration;
\item Part 328, Abstract test suite: Building services: Heating,
   ventilation, and air conditioning;
\item Part 329, Abstract test suite: Exchange of design and
   manufacturing product information for forged parts;
\item Part 330, Abstract test suite: Building structural frame:
   Steelwork;
\item Part 331, Abstract test suite: Process engineering data:
   Process design and process specification of major equipment;
\item Part 501, Application interpreted construct: Edge-based
   wireframe;
\item Part 502, Application interpreted construct: Shell-based
   wireframe;
\item Part 503, Application interpreted construct: Geometrically
   bounded 2D wireframe;
\item Part 504, Application interpreted construct: Draughting
   annotation;
\item Part 505, Application interpreted construct: Drawing structure
   and administration;
\item Part 506, Application interpreted construct: Draughting
   elements;
\item Part 507, Application interpreted construct: Geometrically
   bounded surface;
\item Part 508, Application interpreted construct: Non-manifold
   surface;
\item Part 509, Application interpreted construct: Manifold surface;
\item Part 510, Application interpreted construct: Geometrically
   bounded wireframe;
\item Part 511, Application interpreted construct: Topologically
   bounded surface;
\item Part 512, Application interpreted construct: Faceted boundary
   representation;
\item Part 513, Application interpreted construct: Elementary
   boundary representation;
\item Part 514, Application interpreted construct: Advanced boundary
   representation;
\item Part 515, Application interpreted construct: Constructive
   solid geometry;
\item Part 516, Application interpreted construct: Mechanical design
   context;
\item Part 517, Application interpreted construct: Mechanical design
   geometric presentation;
\item Part 518, Application interpreted construct: Mechanical design
   shaded representation.
\end{itemize}
%</fwd2>
%    \end{macrocode}
%
%    The following is the contents of the file \file{stpdvlst.tex}. It lists
%    the STEP documentation divisions.
%    \begin{macrocode}
%<*fwd3>
  %%%% stpdvlst.tex  STEP documentation divisions
%
\begin{itemize}
\item Parts 11 to 13 specify the description methods,
\item Parts 21 to 26 specify the implementation methods,
\item Parts 31 to 35 specify the conformance testing methodology and
   framework,
\item Parts 41 to 49 specify the integrated generic resources, 
\item Parts 101 to 106 specify the integrated application resources,
\item Parts 201 to 231 specify the application protocols,
\item Parts 301 to 331 specify the abstract test suites, and
\item Parts 501 to 518 specify the application interpreted
   constructs.
\end{itemize}
%</fwd3>
%<*step>
%    \end{macrocode}
%
% \subsubsection{The introduction}
%
% \begin{environment}{Introduction}
%    Starts a new `introduction' clause, together with initial STEP boilerplate.
%    Use as:
%    |\begin{Introduction}{|\meta{class name}|}|
%    where \meta{class name} is one of `description methods', `integrated
%    resources', etc.
% \changes{v1}{1995/05/31}{Added AICs to introduction text.}
%    \begin{macrocode}
\newenvironment{Introduction}[1]{%
\clearpage
\begin{introduction}

ISO 10303 is an International Standard for the computer-interpretable
representation and exchange of product data. The objective is to 
provide a neutral mechanism capable of describing product data 
throughout the life cycle of a product independent from any 
particular system. The nature of this description makes it suitable 
not only for neutral file exchange, but also as a basis for
implementing and sharing product databases and archiving.

This International Standard is organized as a series of parts, 
each published separately. 
The parts of ISO~10303 fall into one of the following series: 
description methods, integrated resources, 
application interpreted constructs, application protocols, 
abstract test suites, implementation methods, 
and conformance testing. 
The series are described in ISO 10303--1. This part of ISO~10303 
is a member of the #1 series.
}%
{\end{introduction}}
%    \end{macrocode}
% \end{environment}
%
% \begin{environment}{majorsublist}
%    This environment provides boilerplate text and an itemiized listing
%    for major subdivisions of the standard.
%    \begin{macrocode}
\newenvironment{majorsublist}{%
\majorsubname 
\begin{itemize}}{\end{itemize}}
%    \end{macrocode}
% \end{environment}
%
% \begin{macro}{\majorsubname}
%    Boilerplate for introduction to major subdivision listing.
%    \begin{macrocode}
\newcommand{\majorsubname}{%
  Major subdivisions of this International Standard are:}
%    \end{macrocode}
% \end{macro}
%
% \subsubsection{Miscellaneous headings}
%
%    Here we define the commands to produce `standard' clause headings.
%    Some of these are general in nature while others are specific
%    to IR parts.
%
% \begin{macro}{\partidefhead}
%    Starts a `Terms defind in ISO 10303-1' subclause
%    \begin{macrocode}
\newcommand{\partidefhead}{\sclause{Terms defined in ISO~10303-1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\refdefhead}
%    Starts a `Terms defined in ' subclause
%    \begin{macrocode}
\newcommand{\refdefhead}[1]{\sclause{Terms defined in #1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\otherdefhead}
%    Starts a `Other definitions' subclause
%    \begin{macrocode}
\newcommand{\otherdefhead}{\sclause{Other definitions}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\schemahead}
%    Identification of a clause describing an EXPRESS schema.
%    \begin{macrocode}
\let\schemahead=\clause
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\introsubhead}
%    Starts an `Introduction' subclause.
%    \begin{macrocode}
\newcommand{\introsubhead}{\sclause{\introductionname}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\fcandasubhead}
%    Starts a `Fundamental concepts and assumptions' subclause.
%    \begin{macrocode}
\newcommand{\fcandasubhead}{\sclause{\fcandaname}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\typehead}
%    Starts a `type definitions' subclause.
%    \begin{macrocode}
\newcommand{\typehead}[1]{\sclause{#1 type definitions}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\atypehead}
%    Starts a `type definition' subsubclause.
%    \begin{macrocode}
\newcommand{\atypehead}[1]{\ssclause{#1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\entityhead}
%    Starts an `entity definitions' subclause. Use as: \\
%    |\entityhead{|\meta{schema}|}{|\meta{group}|}| where \meta{schema}
%    is the name of the schema and \meta{group} is a possibly blank
%    grouping identifier.
%    \begin{macrocode}
\newcommand{\entityhead}[2]{%
  \if\stepemptystring{#2}
     \sclause{#1 entity definitions}
  \else
     \sclause{#1 entity definitions: #2}
  \fi
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\anentityhead}
%    Starts an `entity definition' subsubclause.
%    \begin{macrocode}
\newcommand{\anentityhead}[1]{\ssclause{#1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\rulehead}
%    Starts a `rule definitions' subclause.
%    \begin{macrocode}
\newcommand{\rulehead}[1]{\sclause{#1 rule definitions}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\arulehead}
%    Starts a `rule definition' subsubclause.
%    \begin{macrocode}
\newcommand{\arulehead}[1]{\ssclause{#1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\functionhead}
%    Starts a `function definitions' subclause.
%    \begin{macrocode}
\newcommand{\functionhead}[1]{\sclause{#1 function definitions}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\afunctionhead}
%    Starts a `function definition' subsubclause.
%    \begin{macrocode}
\newcommand{\afunctionhead}[1]{\sclause{#1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\shortnamehead}
%    Starts a `Short names of entities' normative annex
%    \begin{macrocode}
\newcommand{\shortnamehead}{\normannex{Short names of entities}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\objreghead}
%    Starts a `Information object registration' normative annex.
%    \begin{macrocode}
\newcommand{\objreghead}{\normannex{Information object registration}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\docidhead}
%    Starts a `Document identification' subclause.
%    \begin{macrocode}
\newcommand{\docidhead}{\sclause{Document identification}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\schemidhead}
%    Starts a `Schema identification' subclause
%    \begin{macrocode}
\newcommand{\schemaidhead}{\sclause{Schema identification}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aschemidhead}
%    Starts a `Schema identification' subsubclause
%    \begin{macrocode}
\newcommand{\aschemaidhead}[1]{\ssclause{#1 identification}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\expresshead}
%    Starts a `EXPRESS listing' informative annex
%    \begin{macrocode}
\newcommand{\expresshead}{\infannex{\protect\Express\ listing}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\expressghead}
%    Starts a `EXPRESS-G figures' informative annex
%    \begin{macrocode}
\newcommand{\expressghead}{\infannex{\protect\ExpressG\ figures}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\modelscopehead}
%    Starts a `Model scope' informative annex
%    \begin{macrocode}
\newcommand{\modelscopehead}{\infannex{Model scope}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\picshead}
%    Starts a `Protocol Implementation Conformance Statement (PICS) proforma'
%    normative annex
%    \begin{macrocode}
\newcommand{\picshead}{\normannex{Protocol Implementation 
    Conformance Statement (PICS) proforma}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\techdischead}
%    Starts a `Technical discussions' informative annex.
%    \begin{macrocode}
\newcommand{\techdischead}{\infannex{Technical discussions}}
%    \end{macrocode}
% \end{macro}
%
% \subsubsection{Miscellaneous boilerplate}
%
% \begin{macro}{\docreg}
%    Boilerplate for document registration annex. Use as: \\
%    |\docreg{|\meta{version no}|}|
% \changes{v1}{1995/05/31}{Changed ISO 8824 to ISO/IEC 8824.}
%    \begin{macrocode}
\newcommand{\docreg}[1]{%
  To provide for unambiguous identification of an information
  object in an open system, the object identifier
  \begin{center}
  \{~iso standard 10303 part(\thespartno) version(#1)~\}
  \end{center}
  is assigned to this part of ISO~10303. The meaning of this value is defined
  in ISO/IEC~8824-1, and is described in ISO~10303-1.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\schemareg}
%    Boilerplate for EXPRESS schema registration. Use as: \\
%    |\schemareg{|\meta{version no}|}{|
%    \meta{underscored schema}|}{|\meta{object no}|}{|
%    \meta{hyphenated schema}|}{|\meta{schema no}|}{|
%    \meta{clause/annex no}|}|
% \changes{v1}{1995/05/31}{Changed ISO 8824 to ISO/IEC 8824.}
%    \begin{macrocode}
\newcommand{\schemareg}[6]{%
  To provide for unambiguous identification of the #2 
  in an open information system, the object identifier
  \begin{center}
  \{~iso standard 10303 part(\thespartno) version(#1) object(#3) #4(#5)~\}
  \end{center}
  is assigned to the #2 schema (see #6). The meaning of this 
  value is defined in ISO/IEC~8824-1, and is described in ISO~10303-1.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apschemareg}
%    Boilerplate for AP schema registrations. Use as: \\
%    |\apschemareg{|\meta{version no}|}{|
%    \meta{underscored schema}|}{|\meta{object no}|}{|
%    \meta{hyphenated schema}|}{|\meta{long schema no}|}{|
%    \meta{short schema no}|}|
% \changes{v1}{1995/05/31}{Changed ISO 8824 to ISO/IEC 8824.}
%    \begin{macrocode}
\newcommand{\apschemareg}[6]{%
  To provide for unambiguous identification of the 
  schema specifications given in this application protocol #2 
  in an open information system, object identifiers are assigned
  as follows:
  \begin{center}
  \{~iso standard 10303 part(\thespartno) version(#1) object(#3) #4(#5)~\}
  \end{center}
  is assigned to the #2 expanded schema (see annex~A).

  \begin{center}
  \{~iso standard 10303 part(\thespartno) version(#1) object(#3) #4(#6)~\}
  \end{center}
  is assigned to the #2 short form schema (see 5.2).

  The meaning of these 
  values is defined in ISO/IEC~8824-1, and is described in ISO~10303-1.
}
%    \end{macrocode}
% \end{macro}
%
%
% \subsection{Common references}
%
%    Many of the STEP parts use the same `standard' references.
% \begin{macro}{\nrefparti}
% \begin{macro}{\nrefpartxi}
% \begin{macro}{\nrefasni}
%    These macros specify some standard normative references.
%    \begin{macrocode}
\newcommand{\nrefparti}{\isref{ISO 10303-1:1994}{%
           Industrial automation ssystems and integration ---
           Product data representation and exchange ---
           Part 1: Overview and fundamental principles.}}
\newcommand{\nrefpartxi}{\isref{ISO 10303-11:1994}{%
           Industrial automation ssystems and integration ---
           Product data representation and exchange ---
           Part 11: Description methods: The EXPRESS language reference manual.}}
\newcommand{\nrefasni}{\isref{ISO/IEC 8824-1:1994}{%
           Information technology ---
           Open systems interconnection ---
           Abstract syntax notation one (ASN.1) ---
           Part 1: Specification of basic notation.}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\bibidfo}
% \begin{macro}{\brefidfo}
% \begin{macro}{\bibidefix}
% \begin{macro}{\brefidefix}
%    These macros specify some bibliographic references and the associated
%    commands to cite them in the text.
%    \begin{macrocode}
\newcommand{\bibidefo}{\reference{}{%
           IDEF0 (ICAM Definition Language 0),}{%
           Federal Information Processing Standards Publication 183,
           Integration Definition for Information Modeling (IDEF0),
           FIPS PUB 183, National Institute for Standards and
           Technology, December 1993.}\label{bibidefo}}
\newcommand{\brefidefo}{\bref{bibidefo}}
\newcommand{\bibidefix}{\reference{}{%
           IDEF1X (ICAM Definition Language 1 Extended),}{%
           Federal Information Processing Standards Publication 184,
           Integration Definition for Information Modeling (IDEF1X),
           FIPS PUB 184, National Institute for Standards and
           Technology, December 1993.}\label{bibidefix}}
\newcommand{\brefidefix}{\bref{bibidefix}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
%
%
% \subsection{Cover sheet}
%
%    STEP documents require a cover sheet for tracking purposes.
%
% \begin{macro}{\STEPcover}
%    The cover sheet is specified by clever use of the |picture| environment
%    and by using a multitude of internal commands.
%    \begin{macrocode}
\long\def\STEPcover#1{%
%    \end{macrocode}
%    Define the internal commands. These place text into a picture.
% \begin{macro}{\wg}
% \begin{macro}{\thewg}
%    Working group number.
%    \begin{macrocode}
\def\wg##1{\gdef\thewg{##1}\put(44.5,235){\Large\bf ##1}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\docnumber}
%    Document number.
%    \begin{macrocode}
\def\docnumber##1{\put(77,235){\Large\bf ##1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\scivnumber}
%    SC4 number for ballot documents. Only print if called for.
%    (The box has to be lowered a little bit from the baseline to take
%    account of the descendent part of the slash.)
%    \begin{macrocode}
\def\scivnumber##1{\put(159,234){%
    \makebox(0,0)[br]{and also {\Large\bf TC184/SC4 N##1}}}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\projnumber}
%    Project number. Only print if called for.
%    \begin{macrocode}
\def\projnumber##1{\put(60,235){\bf /P##1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\docdate}
%    Document date.
%    \begin{macrocode}
\def\docdate##1{\put(12.5,222.5){##1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\oldwg}
% \begin{macro}{\olddocnumber}
% \begin{macro}{\oldprojnumber}
%    Developers of the immediately prior version of the document.
%    \begin{macrocode}
\def\oldwg##1{\put(110,222.5){\bf ##1}}
\def\olddocnumber##1{\put(130,222.5){\bf ##1}}
\def\oldprojnumber##1{\put(140,222.5){\bf (P##1)}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\partnumber}
%    The part number.
%    \begin{macrocode}
\def\partnumber##1{\put(17.5,205){\large ##1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\doctitle}
%    Informal document title
%    \begin{macrocode}
\def\doctitle##1
{\put(45,207.5){\makebox(0,0)[tl]{\parbox[l]{110mm}{\large
\setlength{\baselineskip}{7.5mm} ##1}}}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\status}
% \begin{macro}{\primcont}
% \begin{macro}{\issue}
% \begin{macro}{\altprop}
% \begin{macro}{\partialcont}
%    Document status and type of content.
%    \begin{macrocode}
\def\status##1{\put(120,180){##1}}
\newcommand{\primcont}{\put(5,185){X}}
\newcommand{\issue}{\put(5,180){X}}
\newcommand{\altprop}{\put(5,175){X}}
\newcommand{\partialcont}{\put(5,170){X}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\abstract}
% \begin{macro}{\keywords}
% \begin{macro}{\comread}
%    Document abstract, keywords, and comments to the reader.
%    \begin{macrocode}
\long\def\abstract##1{%
\put(80,161){\makebox(0,0)[t]{\parbox[l]{155mm}{##1}}}}
\long\def\keywords##1{%
\put(27.5,120){\makebox(0,0)[t]{\parbox[l]{50mm}{##1}}}}
\long\def\comread##1{%
\put(80,32.5){\makebox(0,0)[t]{\parbox[l]{150mm}{##1}}}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\datepd}
% \begin{macro}{\daterd}
% \begin{macro}{\datequal}
% \begin{macro}{\datetc}
% \begin{macro}{\dateec}
% \begin{macro}{\dateisocd}
% \begin{macro}{\daterel}
% \begin{macro}{\datetech}
% \begin{macro}{\dateapp}
%    Dates the document passed various life cycle stages.
%    \begin{macrocode}
%     project leader signoff
\def\dateproj##1{\put(60,110){##1}}
\def\datepd##1{\put(60,110){##1}%
     \typeout{Command \string\datepd{} is deprecated. Use \string\dateproj{}
              instead.}}
%     WG convenor signoff
\def\datewg##1{\put(60,105){##1}}
\def\daterd##1{\put(60,105){##1}%
     \typeout{Command \string\daterd{} is deprecated. Use \string\datewg{}
              instead.}}
%     Qualification signoff
\def\datequal##1{\put(60,100){##1}}
%     Integration signoff
\def\dateint##1{\put(60,95){##1}}
\def\datetc##1{\put(60,95){##1}%
     \typeout{Command \string\datetc{} is deprecated. Use \string\dateint{}
              instead.}}
%     editorially complete
\def\dateec##1{\put(60,90){##1}}
%     ISO committee draft
%\def\dateisocd##1{\put(60,85){##1}}
\def\dateisocd##1{%
     \typeout{Command \string\dateisocd{} is not used any more.}}
%     other doc project lead  signoff
\def\dateprojo##1{\put(141,110){##1}}
\def\daterel##1{\put(141,110){##1}%
     \typeout{Command \string\daterel{} is deprecated. Use \string\dateprojo{}
              instead.}}
%     other doc WG signoff
\def\datewgo##1{\put(141,105){##1}}
\def\datetech##1{\put(141,105){##1}%
     \typeout{Command \string\datetech{} is deprecated. Use \string\datewgo{}
              instead.}}
%     other Qualification signoff
\def\datequalo##1{\put(141,100){##1}}
\def\dateapp##1{\put(141,100){##1}%
     \typeout{Command \string\dateapp{} is deprecated. Use \string\datequalo{}
              instead.}}
%    other Integration signoff
\def\dateinto##1{\put(141,95){##1}}
%    other Editorially apporoved
\def\dateeco##1{\put(141,90){##1}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\owner}
% \begin{macro}{\address}
% \begin{macro}{\telephone}
% \begin{macro}{\email}
%    Contact information for the document's owner/editor.
%    \begin{macrocode}
\def\owner##1{\put(32.5,77.5){##1}}
\def\address##1{%
\put(48,75){\makebox(0,0)[t]{\parbox[l]{57.5mm}{##1}}}}
\def\telephone##1{\put(35,47.5){##1}}
\def\email##1{\put(17.5,42.5){##1}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\altowner}
% \begin{macro}{\altaddress}
% \begin{macro}{\alttelephone}
% \begin{macro}{\altemail}
%    Contact information for the document's alternate owner/editor.
%    \begin{macrocode}
\def\altowner##1{\put(105,77.5){##1}}
\def\altaddress##1{%
\put(128.5,75){\makebox(0,0)[t]{\parbox[l]{57.5mm}{##1}}}}
\def\alttelephone##1{\put(117.5,47.5){##1}}
\def\altemail##1{\put(100,42.5){##1}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
% \end{macro}
%
%    Having finished the local commands, make sure we have an 
%    empty page style.
%    \begin{macrocode}
\protect\thispagestyle{nohead}
%    \end{macrocode}
%    Start the picture.
%    \begin{macrocode}
\setlength{\unitlength}{1mm}
\begin{picture}(159,221.5)(0,13.5)
\thicklines
%    \end{macrocode}
%    Draw the heading block
%    \begin{macrocode}
\put(0,235){{\Large\bf ISO TC184/SC4/}}
\put(72,235){\Large\bf N}
\put(44.5,234){\line(1,0){20}}
\put(77,234){\line(1,0){12.5}}
%    \end{macrocode}
%   Identify the date slot.
%    \begin{macrocode}
\put(0,222.5){\bf Date:}
%    \end{macrocode}
%    Identify the slots for the superseded document information.
%    \begin{macrocode}
\put(75,222.5){\bf Supersedes SC4/}
\put(125,222.5){\bf N} 
\put(107.5,221.5){\line(1,0){15}}
\put(130,221.5){\line(1,0){10}}
%    \end{macrocode}
%    Draw the STEP title.
%    \begin{macrocode}
\put(80,215){
  \makebox(0,0)[b]{\large\bf PRODUCT DATA REPRESENTATION AND EXCHANGE}}
%    \end{macrocode}
%    Draw the major box.
%    \begin{macrocode}
%  major box
\put(0,81){\framebox(159,131.5){}}
%    \end{macrocode}
%    Identify the part and informal title.
%    \begin{macrocode}
\put(5,205){\large \bf Part:}
\put(30,205){\large \bf Title:}
\multiput(45,204)(0,-7.5){2}{\line(1,0){110}}
%    \end{macrocode}
%    Draw slots for document purpose.
%    \begin{macrocode}
\put(2,190){Purpose of this document as it relates to the target document is:}
\put(12,185){Primary Content}
\put(12,180){Issue Discussion}
\put(12,175){Alternate Proposal}
\put(12,170){Partial Content}
\multiput(2.5,184)(0,-5){4}{\line(1,0){7.5}}
%    \end{macrocode}
%    Current status slot.
%    \begin{macrocode}
\put(90,180){\large Current Status:}
\put(120,179){\line(1,0){35}}
%    \end{macrocode}
%    Draw abstract and keyword headings.
%    \begin{macrocode}
\put(2,163){\bf ABSTRACT:}
\put(2,122.5){\bf KEYWORDS:}
%    \end{macrocode}
%     Draw status history box.
%    \begin{macrocode}
\put(109,122.5){\makebox(0,0)[b]{{\bf Document Status/Dates} (dd/mm/yy)}}
\put(57.5,82.5){\framebox(101,36.5){}}
%  don't need the vertical line anymore
%\put(117.5,82.5){\line(0,1){36.5}}
%    \end{macrocode}
%     History for standard documents.
%    \begin{macrocode}
\put(60,115){\makebox(0,0)[bl]{{\bf Part Documents}}}
\put(108,110){\makebox(0,0)[bc]{Project Leader}}
\put(108,105){\makebox(0,0)[bc]{Working Group Convenor}}
\put(108,100){\makebox(0,0)[bc]{Qualification}}
\put(108,95){\makebox(0,0)[bc]{Integration}}
\put(108,90){\makebox(0,0)[bc]{Editing}}
%  \put(60,115){Part Documents}
%  \put(77.5,110){Project Leader}
%  \put(77.5,105){Working Group}
%  \put(77.5,100){Qualification}
%  \put(77.5,95){Integration}
%  \put(77.5,90){Editorially Complete}
%  \put(77.5,85){ISO Committee Draft}
%  \multiput(60,109)(0,-5){6}{\line(1,0){15}}
\multiput(60,109)(0,-5){5}{\line(1,0){15}}
%    \end{macrocode}
%    History for other documents.
%    \begin{macrocode}
%    non-part history
%  \put(120,115){Other SC4 Documents}
\put(156,115){\makebox(0,0)[br]{{\bf Other SC4 Documents}}}
\multiput(156,109)(0,-5){5}{\line(-1,0){15}}
%  \put(137.5,110){Author}
%  \put(137.5,105){PPC}
%  \put(137.5,100){SC4}
%  \put(137.5,95){Technically}
%  \put(137.5,90){Complete}
%  \put(137.5,85){Approved}
%  \multiput(120,109)(0,-5){3}{\line(1,0){15}}
%  \put(120,84){\line(1,0){15}}
%    \end{macrocode}
%    Owner information.
%    \begin{macrocode}
\put(80,40){\line(0,1){41}}
\put(0,77.5){\bf Owner/Editor:}
\put(0,72.5){\bf Address:}
\put(0,47.5){\bf Telephone/FAX:}
\put(0,42.5){\bf E-mail:}
%    \end{macrocode}
%    Alternate owner information.
%    \begin{macrocode}
%      alternate address
\put(82,77.5){\bf Alternate:}
\put(82,72.5){\bf Address:}
\put(82,47.5){\bf Telephone/FAX:}
\put(82,42.5){\bf E-mail:}
%    \end{macrocode}
%     Comments to reader box.
%    \begin{macrocode}
\put(5,35){{\bf Comments to Reader}}
\put(0,0){\framebox(159,40){}}
%    \end{macrocode}
%     Revision notice for the cover sheet layout.
%    \begin{macrocode}
\put(159,-1){\makebox(0,0)[tr]{{\tiny revision 5, 4/96 (PRW)}}}
%    \end{macrocode}
%     Finish off the picture.
%    \begin{macrocode}
#1
\end{picture}
\setlength{\unitlength}{1pt}
%    \end{macrocode}
%    Force printing of cover sheet.
%    \begin{macrocode}
\clearpage
%    \end{macrocode}
%    At last, this is the end of the definition of the |\STEPcover| command.
%    \begin{macrocode}
}
%    \end{macrocode}
% \end{macro}
%    The end of this package.
%    \begin{macrocode}
%</step>
%    \end{macrocode}
%
% \section{The Integrated Resources package}
%
%    This section defines the content of the package designed for use
%    in documenting STEP Integrated Resources.
%    \begin{macrocode}
%<*ir>
%    \end{macrocode}
%
% \subsection{Boilerplate}
%
%    This section defines the commands used to print boilerplate text.
%
% \begin{macro}{\irshortnames}
%    Boilerplate for IR Short Name annex.
%    \begin{macrocode}
\newcommand{\irshortnames}{%
  Table A.1 provides the short names of entities specified in this 
part of ISO~10303. Requirements on the use of short names are 
found in the implementation methods included in ISO~10303.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\irexplisting}
%    Boilerplate for introduction to IR EXPRESS listing annex.
%    \begin{macrocode}
\newcommand{\irexplisting}{%
  This annex provides a listing of the short names and a listing 
of the \Express\ specified in this part of ISO~10303. No text or 
annotation is included. This annex is provided only in 
computer-interpretable form.
\begin{anote}The information provided on this diskette is informative; 
       the normative text is that contained in the body of this 
       part of ISO~10303.\end{anote}
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\irexpressg}
%    Boilerplate for IR EXPRESS-G annex. Use as: \\
%    |\irexpressg{|\meta{figure range}|}|
%    \begin{macrocode}
\newcommand{\irexpressg}[1]{%
  #1 correspond to the \Express\ listing given in annex~C. The
diagrams use the \ExpressG\ graphical notation for the 
\Express\ language. \ExpressG\ is defined in annex~D 
of ISO 10303-11.
}
%    \end{macrocode}
% \end{macro}
%
%
%    The end of this package.
%    \begin{macrocode}
%</ir>
%    \end{macrocode}
%
%
% \section{The Application Protocol package}
%
%    This section defines the content of the package designed for use
%    in documenting STEP Application Protocols.
%    \begin{macrocode}
%<*ap>
%    \end{macrocode}
%
% \subsection{Preamble commands}
%
%    These commands, if used, should be placed in the document preamble.
%
% \begin{macro}{\aptitle}
% \begin{macro}{\theap}
%    |\aptitle{|\meta{title of AP}|}| --- the AP title to be used in 
%    running text.
%    \begin{macrocode}
\gdef\theap{}
\newcommand{\aptitle}[1]{\gdef\theap{#1}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\ifaicinap}
%    Set up for use of AIC's in the AP. Initialize to no AIC used.
%    \begin{macrocode}
\newif\ifaicinap
\aicinapfalse
%    \end{macrocode}
% \end{macro}
%
%
% \subsection{Heading commands}
%
%    The commands in this section provide for the `standard' clause
%    headings in an AP.
%
% \begin{macro}{\inforeqhead}
%    Starts a `Information requirements' clause
%    \begin{macrocode}
\newcommand{\inforeqhead}{\clause{Information requirements}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\uofhead}
%    Starts a `Units of functionality' subclause
%    \begin{macrocode}
\newcommand{\uofhead}{\sclause{Units of functionality}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\auofhead}
%    Starts a subsubclause for a UoF
%    \begin{macrocode}
\newcommand{\auofhead}[1]{\ssclause{#1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\applobjhead}
%    Starts a `Application objects' subclause
%    \begin{macrocode}
\newcommand{\applobjhead}{\sclause{Application objects}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\applasserthead}
%    Starts a `Application assertions' subclause
%    \begin{macrocode}
\newcommand{\applasserthead}{\sclause{Application assertions}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimhead}
%    Starts a `Application interpreted model' clause
%    \begin{macrocode}
\newcommand{\aimhead}{\clause{Application interpreted model}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\maptablehead}
%    Starts a `Mapping table' subclause
%    \begin{macrocode}
\newcommand{\maptablehead}{\sclause{Mapping table}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimshortexphead}
%    Starts a `AIM EXPRESS short listing' subclause
%    \begin{macrocode}
\newcommand{\aimshortexphead}{\sclause{AIM \protect\Express\ short listing}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\confreqhead}
%    Starts a `Conformance requirements' clause
%    \begin{macrocode}
\newcommand{\confreqhead}{\clause{Conformance requirements}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimlongexphead}
%    Starts a `AIM EXPRESS exapnded listing' normative annex
%    \begin{macrocode}
\newcommand{\aimlongexphead}{\normannex{AIM \protect\Express\ expanded listing}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimshortnameshead}
%    Starts a `AIM short names' normative annex
%    \begin{macrocode}
\newcommand{\aimshortnameshead}{\normannex{AIM short names}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\impreqhead}
%    Starts a `Implementation method specific requirements' normative annex
%    \begin{macrocode}
\newcommand{\impreqhead}{\normannex{Implementation method 
    specific requirements}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aamhead}
%    Starts a `Application activity model' informative annex
%    \begin{macrocode}
\newcommand{\aamhead}{\infannex{Application activity model}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aamdefhead}
%    Starts a `Application activity model definitions and abbreviations' subclause
%    \begin{macrocode}
\newcommand{\aamdefhead}{\sclause{Application activity model 
     definitions and abbreviations}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aamfighead}
%    Starts a `Application activity model diagrams' subclause
%    \begin{macrocode}
\newcommand{\aamfighead}{\sclause{Application activity model diagrams}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\armhead}
%    Starts a `Application reference model' informative annex
%    \begin{macrocode}
\newcommand{\armhead}{\infannex{Application reference model}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimexpressghead}
%    Starts a `AIM EXPRESS-G' informative annex
%    \begin{macrocode}
\newcommand{\aimexpressghead}{\infannex{AIM \protect\ExpressG{}}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimexpresshead}
%    Starts a `AIM EXPRESS listing' informative annex
%    \begin{macrocode}
\newcommand{\aimexpresshead}{\infannex{AIM \protect\Express\ listing}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apusagehead}
%    Starts a `Application protocol usage guide' informative annex
%    \begin{macrocode}
\newcommand{\apusagehead}{\infannex{Application protocol usage guide}}
%    \end{macrocode}
% \end{macro}
%
%
%
%
%
% \subsection{Boilerplate printing}
%
% \begin{macro}{\apintroend}
%     Print boilerplate for end of AP introduction clause.
%    \begin{macrocode}
\newcommand{\apintroend}{\input{apendint}}
%    \end{macrocode}
%
%    Here is the text of \file{apendint.tex}.
%    \begin{macrocode}
%</ap>
%<*apf1>
   %%%%  apendint.tex   Boilerplate for end of AP introduction clause.
%

    Application protocols provide the basis for developing 
implementations of ISO~10303 and abstract test suites for 
the conformance testing of AP implementations.

    Clause~1 defines the scope of the application protocol 
and summarizes  the functionality and data covered by the AP. 
Clause~3 lists the words defined in this part of ISO~10303 and
gives pointers to words defined elsewhere.
An application activity model that is the basis for the definition 
of the scope is provided in annex~F. The information requirments 
of the application are specified in clause~4 using terminology 
appropriate to the application. A graphical representation of the
information requirements, referred to as the application reference 
model, is given in annex~G.

    Resource constructs are interpreted to meet the information
requirements. This interpretation produces the application
interpreted model (AIM). This interpretation, given in 5.1, shows
the correspondence between the information requirements and the
AIM. The short listing of the AIM specifies the interface to the
integrated resources and is given in 5.2. Note that the definitions
and \Express\ provided in the the integrated resources for constructs
used in the AIM may include select list items and subtypes which are
not imported into the AIM. The expanded listing given in annex~A
contains the complete \Express\ for the AIM without annotation. A
graphical representation of the AIM is given in annex~H. Additional
requirements for specific implementation methods are given in
annex~D.

%</apf1>
%<*ap>
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apscope}
%    Print boilerplate for start of AP scope clause. \\
%     |\apscope{|\meta{application purpose and context}|}|
%    \begin{macrocode}
\newcommand{\apscope}[1]{%
  This part of ISO 10303 specifies the use of the integrated 
resources necessary for the scope and information requirements 
for #1

\begin{anote}The application activity model in annex F provides a 
       graphical representation of the processes and 
       information flows which are the basis for the definition 
       of the scope of this part of ISO~10303.\end{anote}
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apinforeq}
%    Print boilerplate for start of AP clause on 
%    information requirements. \\
%     |\apinforeq{|\meta{AP purpose}|}|
% \changes{v1}{1995/05/31}{Added AIC phrase (twice).}
%    \begin{macrocode}
\newcommand{\apinforeq}[1]{%
  This clause specifies the information required for #1

  The information requirements are specified as a set of 
units of functionality, application objects, and 
application assertions. These assertions pertain to
individual application objects and to relationships 
between application objects. The information requirements 
are defined using the terminology of the subject area of 
this application protocol.

\begin{notes}
\begin{note}A graphical representation of the information requirements 
      is given in annex~G.\end{note}
\begin{note}The information requirements correspond to those of the 
      activities identified as being within the scope of this 
      application protocol in annex~F.\end{note}
\begin{note}The mapping table specified in 5.1 shows how the 
      integrated  resources 
      \ifaicinap and application interpreted constructs \fi
      are used to meet the information requirements of this
      application protocol. \end{note}
\end{notes}
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apuof}
%    Print boilerplate for UoF. \\
%     |\apuof{|\meta{UoF list}|}| where \meta{UoF list} is a list of
%     UoF names in |\item| format.
%
%    \begin{macrocode}
\newcommand{\apuof}[1]{%
  This subclause specifies the units of functionality for the 
\theap\space application protocol. This part of ISO~10303 
specifies the following units of functionality:
\begin{itemize}
  #1
\end{itemize}

  The units of functionality and a description of the functions 
that each UoF supports are given below. The application objects 
included in the UoFs are defined in 4.2. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apapplobj}
%   Print boilerplate for Application objects.
%
%    \begin{macrocode}
\newcommand{\apapplobj}{%
  This subclause specifies the application objects for 
the \theap\space application protocol. Each application 
object is an atomic element that embodies a unique 
application concept and contains attributes specifying 
the data elements of the object. The application objects 
and their definitions are given below. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apassert}
%   Print boilerplate for AP application assertions subclause.
%
%    \begin{macrocode}
\newcommand{\apassert}{%
  This subclause specifies the application assertions for the 
\theap\space application protocol. Application assertions 
specify the relationships between application objects, 
the cardinality of the relationships, and the rules required 
for the integrity and validity of the application objects and
UoFs. The application assertions and their definitions are given below.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apmappingtable}
%   Print boilerplate for start of AP mapping table subclause. 
%
% \changes{v1}{1995/05/31}{Major rewrite of mapping table boilerplate.}
% \changes{v1}{1995/05/31}{Ignore parameters in mapping table boilerplate.}
%    \begin{macrocode}
\newcommand{\apmappingtable}{\input{apmptbl}}
%    \end{macrocode}
%
%    Here is the contents of the \file{apmptbl.tex} file.
%    \begin{macrocode}
%</ap>
%<*apf2>
   %%% apmptbl.tex  mapping table boilerplate
  This clause contains the mapping table that shows how each 
UoF and application object of this part of ISO~10303 
(see clause~4) maps to one or more AIM constructs 
(see annex~A).
The mapping table is organized in five columns.

\begin{itemize}
\item Column 1) Application element: Name of an application 
    element as it appears in the application object definition 
    in 4.2. Application object names are written in uppercase. 
    Attribute names and assertions are listed after the application
    object to which they belong and are written in lower case.
\item Column 2) AIM element: Name of an AIM element as it 
    appears in the AIM (see annex~A), the term `IDENTICAL MAPPING',
    or the term `PATH'. AIM entities are written in lower case. 
    Attribute names of AIM entities are referred to as
    $<$entity name$>.<$attribute name$>$. The mapping of an
    application element may result in several related AIM
    elements. Each of these AIM elements requires a line of its 
    own in the table. The term `IDENTICAL MAPPING' indicates
    that both application objects of an application assertion
    map to the same AIM element. The term `PATH' indicates
    that the application assertion maps to the entire reference
    path.
\item Column 3) Source: For those AIM elements that are 
    interpreted from the integrated resources, this is the 
    number of the corresponding part of ISO~10303. For those 
    AIM elements that are created for the purpose of this part 
    of ISO~10303, this is the number of this part.
    \ifaicinap  For those AIM elements that are directly 
    incorporated from an application interpreted
    construct (AIC) this is the AIC reference. \fi
\item Column 4) Rules: One or more numbers may be given that 
    refer to rules that apply to the current AIM element or
    reference path. For rules that are derived from 
    relationships between application objects, the same rule
    is referred to by the mapping entries of all the involved AIM
    elements. The expanded names of the rules are listed after
    the table.
\item Column 5) Reference path: To describe fully the mapping 
    of an ARM element, it may be necessary to specify a 
    reference path through several related AIM elements. The
    reference path column documents the role of an AIM element
    relative to the AIM element in the row succeeding it.
    Two or more such related AIM elements define the 
    interpretation of the integrated resources that satisfies 
    the requirement specified by the application object.
    For each AIM element that has been created for use within this 
    part of ISO~10303, a reference path up to its supertype from
    an integrated resource is specified.
\end{itemize}

  For the expression of reference paths the following notational 
conventions apply:
\begin{enumerate}
\item \verb|[]| : multiple AIM elements or sections of the
    reference path are required to satisfy an information
    requirement;
\item \verb|()| : multiple AIM elements or sections of the
    reference path are identified as alternatives within the
    mapping to satisfy an information requirement;
\item \verb|{}| : enclosed section constrains the reference path
    to satisfy an information requirement;
\item \verb|->| : attribute references the entity or select type 
    given in the following row;
\item \verb|<-| : entity or select type is referenced by the
     attribute in the following row;
\item \verb|[i]| : attribute is an aggregation of which a
     single member is given in the following row;
\item \verb|[n]| : attribute is an aggregation of which 
     member \verb|n| is given in the following row;
\item \verb|=>| : entity is a supertype of the entity given in the 
    following row;
\item \verb|<=| : entity is a subtype of the entity given in 
    the following row;
\item \verb|=| : the string, select, or enumeration type is
    constrained to a choice or value;
\item \verb|\| : the line continuations for strings that wrap.
\end{enumerate}
%</apf2>
%<*ap>
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apshortexpress}
%   Print boilerplate for AP AIM EXPRESS short listing.
% \changes{v1}{1995/05/31}{Changed the conditionals.}
%
%    \begin{macrocode}
\newcommand{\apshortexpress}{%
  This clause specifies the \Express\ schema that uses 
elements from the integrated resources
\ifaicinap (and the AICs) \fi
and contains the types, entity specializations, rules, 
and functions that are specific to this part of ISO~10303. 
This clause also specifies modifications to the text 
for constructs that are imported from the
integrated
\ifaicinap resources (and the AICs). \else resources. \fi
The definitions and
\Express\ provided in the integrated resources for constructs 
used in the AIM may include select list items and subtypes 
that are not imported into the AIM. Requirements stated 
in the integrated resources that refer to such items and 
subtypes apply exclusively to those items that are imported 
into the AIM.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apconformance}
%   Print boilerplate for AP conformance. \\
%   |\apconformance{|\meta{implentation methods}|}|
% \changes{v1}{1995/05/31}{Interchanged annexes C and D.}
%    \begin{macrocode}
\newcommand{\apconformance}[1]{%
  Conformance to this part of ISO 10303 includes satisfying 
the requirements stated in this part, the requirements of 
the implementation method(s) supported, and the relevant 
requirements of the normative references.

  An implementation shall support at least one of the following 
implementation methods: #1. 

Requirements with respect to 
implementation methods-specific requirements are specified in annex~C.

  The Protocol Information Conformance Statement (PICS) 
proforma lists the options or the combination of options 
that may be included in the implementation. The PICS 
proforma is provided in annex~D. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apconformclasses}
%   Print boilerplate for AP conformance classes. \\
%   |\apconformclasses{|\meta{class list}|}| where \meta{class list}
%   is a list of conformance classes in |\item| format.
%
%    \begin{macrocode}
\newcommand{\apconformclasses}[1]{%
  This part of ISO~10303 provides for a number of options that 
may be supported by an implementation. These options have been 
grouped into the following conformance classes:
\begin{itemize}
  #1
\end{itemize}
Support for a particular conformance class requires support of 
all the options specified in this class. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apshortnames}
%   Print boilerplate for AP short names.
%
%    \begin{macrocode}
\newcommand{\apshortnames}{%
  Table B.1 provides the short names of entities specified 
in the AIM of this part of ISO~10303. Requirements on the 
use of the short names are found in the implementation methods 
included in ISO~10303. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\picsannex}
%   Print boilerplate for PICS annex.
%
%    \begin{macrocode}
\newcommand{\picsannex}{%
  This clause lists the optional elements of this part 
of ISO~10303. An implementation may choose to support 
any combination of these optional elements. However, 
certain combinations of options are likely to be
implemented together. These combinations are called 
conformance classes and are described in the subclauses 
of this annex.

  This annex is in the form of a questionnaire. This 
questionnaire is intended to be filled out by the 
implementor and may be used in preparation for conformance 
testing by a testing laboratory. The completed PICS proforma
is referred to as a PICS. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apaamintro}
%   Print boilerplate for AAM intro.
%
%    \begin{macrocode}
\newcommand{\apaamintro}{%
  The application activity model (AAM) is provided as an aid 
in understanding the scope and information requirements 
defined in this application protocol. The model is presented 
as a set of activity figures that contain the activity
diagrams and a set of definitions of the activities
and their data.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apaamdefs}
%   Print boilerplate for AAM definitions.
%
%    \begin{macrocode}
\newcommand{\apaamdefs}{%
    The following terms are used in the application 
activity model. Terms marked with an asterisk are outside 
the scope of this application protocol.

    The definitions given in this annex do not supersede 
the definitions given in the main body of the text. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aamfigures}
%   Print boilerplate for AAM figures. \\
%   |\aamfigures{|\meta{figure range}|}{|\meta{name of modeling language}|}|
%
%    \begin{macrocode}
\newcommand{\aamfigures}[2]{%
  The application activity model diagrams are given in #1. The 
graphical form of the application activity model is 
presented in the #2 activity modelling format.
Activities and data flows that are out of scope are 
marked with asterisks. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\armfigures}
%   Print boilerplate for ARM figures. \\
%   |\armfigures{|\meta{figure range}|}{|\meta{name of modeling language}|}|
%
%    \begin{macrocode}
\newcommand{\armfigures}[2]{%
  This annex provides the application reference model for this part of ISO
  10303 and is given in #1. The application reference model is a graphical
  representation of the structure and constraints of the application objects
  specified in clause~4. The graphical form of the application reference
  model is presented in the #2 format. The application reference model is
  independent from any implementation method. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimexpressg}
%   Print boilerplate for AIM EXPRESS-G. \\
%   |\aimexpressg{|\meta{Figure range}|}|
%
%    \begin{macrocode}
\newcommand{\aimexpressg}[1]{%
  #1 correspond to the AIM \Express\ expanded listing given in annex~A. 
The diagrams use the \ExpressG\ graphical notation for the 
\Express\ language. \ExpressG\ is defined in annex~D of 
ISO 10303-11. 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimexplisting}
%   Print boilerplate for AIM EXPRESS.
%
%    \begin{macrocode}
\newcommand{\aimexplisting}{%
  This annex provides a listing of the table of short names 
and a listing of the \Express\ specified in the AIM of this 
part of ISO~10303. No text or annotation is included. This 
annex is provided only in computer-interpretable form.

\begin{anote}The information provided on this diskette is informative; 
       the normative text is that contained in the body of this 
       part of ISO~10303.\end{anote} 
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aimlongexp}
%   Print boilerplate for AIM EXPRESS expanded listing.
%
%    \begin{macrocode}
\newcommand{\aimlongexp}{%
  The following \Express\ is the expanded form of the short
form schema given in~5.2. In the event of any discrepancy
between the short form and this expanded listing, the expanded
listing shall be used.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apimpreq}
%   Print boilerplate for AP requirements on exchange structure.\\
%   |\apimpreq{|\meta{schema name}|}|.
%
%    \begin{macrocode}
\newcommand{\apimpreq}[1]{%
  The implementation method defines what types of exchange
behaviour are required with respect to this part of ISO~10303.
Conformance to this part of ISO~10303 shall be realized in an
exchange structure. The file format shall be encoded according
to the syntax and \Express\ language mapping defined in
ISO~10303-21 and in the AIM defined in annex~A of this part
of ISO~10303. The header of the exchange structure shall identify
use of this part of ISO~10303 by the schema name `#1'.
}
%    \end{macrocode}
% \end{macro}
%
%    The end of this package.
%    \begin{macrocode}
%</ap>
%    \end{macrocode}
%
% \section{The Application Interpreted Construct package}
%
%    This section defines the contents of the package designed for
%    use in documenting STEP AICs.
%    \begin{macrocode}
%<*aic>
%    \end{macrocode}
%
% \subsection{Heading commands}
%
%    The commands in this section provide for the specified clause
%    headings in an AIC.
%
% \begin{macro}{\aicshortexphead}
%    Starts a `EXPRESS short listing' clause
%    \begin{macrocode}
\newcommand{\aicshortexphead}{\clause{\protect\Express\ short listing}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aicshortnameshead}
%    Starts a `Short names of entities' normative annex
%    \begin{macrocode}
\newcommand{\aicshortnameshead}{\normannex{Short names of entities}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aicexpressghead}
%    Starts a `EXPRESS-G diagrams' informative annex
%    \begin{macrocode}
\newcommand{\aicexpressghead}{\infannex{\protect\ExpressG\ figures}}
%    \end{macrocode}
% \end{macro}
%
%
%
% \subsection{Boilerplate commands}
%
% \begin{macro}{\aicextraintro}
%    Print boilerplate for an extra AIC paragraph in the Introduction.
%
%    \begin{macrocode}
\newcommand{\aicextraintro}{%
    An application interpreted construct (AIC) provides a
logical grouping of interpreted constructs that supports
a specific functionality for the usage of product data across
multiple application contexts. An interpreted construct is a
common interpretation of the integrated resources that 
supports shared information requirements among application
protocols.
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aicdef}
%    Boilerplate for the definition of `AIC'. Only to be used within
%    the |definitions| environment.
%    \begin{macrocode}
\newcommand{\aicdef}{%
\definition{application interpreted construct (AIC)}%
           {a logical grouping of interpreted constructs
            that supports a specific functionality for
            the usage of product data across multiple
            application contexts.}
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aicshortexpintro}
%    This environemt provides the boilerplate for the introduction
%    to the AIC EXPRESS short listing.
%   
%    \begin{macrocode}
\newcommand{\aicshortexpintro}{%
    This clause specifies the \Express\ schema that uses 
elements from the integrated resources and contains the
types, entity specializations, and functions that are
specific to this part of ISO~10303.
\begin{note}There may be subtypes and items of select lists that
      appear in the integrated resources that are not
      imported into the AIC. Constructs are eliminated
      from the subtype tree or select list through the
      use of the implicit interface rules of ISO 10303-11.
      References to eliminated constructs are outside the
      scope of the AIC.\end{note} % end note
}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\aicshortnames}
%    Boilerplate for AIC Short Name annex.
%    \begin{macrocode}
\newcommand{\aicshortnames}{%
  Table A.1 provides the short names of entities specified in this 
part of ISO~10303. Requirements on the use of short names are 
found in the implementation methods included in ISO~10303.
}
%    \end{macrocode}
% \end{macro}
%
%
% \begin{macro}{\aicexpressg}
%   Print boilerplate for AIC EXPRESS-G. \\
%   |\aicexpressg{|\meta{Figure range}|}|
%
%    \begin{macrocode}
\newcommand{\aicexpressg}[1]{%
  #1 correspond to the \Express\ generated from the short
listing given in clause~4 using the interface specifications
of ISO 10303-11.
The diagrams use the \ExpressG\ graphical notation for the 
\Express\ language. \ExpressG\ is defined in annex~D of 
ISO 10303-11. 
}
%    \end{macrocode}
% \end{macro}
%
%
%
%
%    The end of this package.
%    \begin{macrocode}
%</aic>
%    \end{macrocode}
%
%
% \section{The Abstract Test Suite package}
%
%    This section defines the contents of the package designed for
%    use in documenting STEP ATSs. The relevent text has been taken from
%    \cite{ATS}.
%
%    \begin{macrocode}
%<*ats>
%    \end{macrocode}
%
% \subsection{Preamble commands}
%
%    These commands must be put in the document preamble.
% \begin{macro}{\APnumber}
% \begin{macro}{\APtitle}
%    |\APnumber{|\meta{part number of AP}|}| --- the part number (e.g. 203)
%    of the AP of this ATS. Internally it is referred to as |\theAPpartno|.
%    \begin{macrocode}
\gdef\theAPpartno{}
\newcommand{\APnumber}[1]{\gdef\theAPpartno{#1}}
%    \end{macrocode}
%    |\APtitle{|\meta{title of AP}|}| --- the title of the AP (to be put in
%    running text). Internally it is referred to as |\theAPtitle|.
%    \begin{macrocode}
\gdef\theAPtitle{}
\newcommand{\APtitle}[1]{\gdef\theAPtitle{#1}}
%    \end{macrocode}
%
% \end{macro}
% \end{macro}
% 
% \subsection{Heading commands}
%
%    The commands in this section provide for the specified clause
%    headings in an ATS.
%
% \begin{macro}{\purposeshead}
% \begin{macro}{\purposesname}
%    Command to start a `Test purposes' clause.
%    \begin{macrocode}
\newcommand{\purposesname}{Test purposes}
\newcommand{\purposeshead}{%
            \clause{\purposename}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\domainpurposehead}
% \begin{macro}{\domainpurposename}
%    Command to start a `Domain test purposes' clause.
%    \begin{macrocode}
\newcommand{\domainpurposename}{Domain test purposes}
\newcommand{\domainpurposehead}{%
            \sclause{\domainpurposename}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\aepurposehead}
% \begin{macro}{\aepurposename}
%    Command to start a `AE test purposes' clause.
%    \begin{macrocode}
\newcommand{\aepurposename}{AE test purposes}
\newcommand{\aepurposehead}{%
            \sclause{\aepurposename}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\apobjhead}
%    Command to start an application object clause.
%    Use as |\apobjhead{|\meta{Application object n}|}|.
%    \begin{macrocode}
\newcommand{\apobjhead}[1]{%
            \ssclause{#1}}
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\apasserthead}
% \begin{macro}{\apassertname}
%    Command to start an `Application assertions' clause.
%    \begin{macrocode}
\newcommand{\apassertname}{Application assertions}
\newcommand{\apasserthead}{%
            \ssclause{\apassertname}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\aimpurposehead}
% \begin{macro}{\aimpurposename}
%    Command to start a `AIM test purposes' clause.
%    \begin{macrocode}
\newcommand{\aimpurposename}{AIM test purposes}
\newcommand{\aimpurposehead}{%
            \sclause{\aimpurposename}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\extrefpurposehead}
% \begin{macro}{\extrefpurposename}
%    Command to start a `External reference test purposes' clause.
%    \begin{macrocode}
\newcommand{\extrefpurposename}{External reference test purposes}
\newcommand{\extrefpurposehead}{%
            \sclause{\extrefpurposename}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\implementpurposehead}
% \begin{macro}{\implementpurposename}
%    Command to start a `Implementation method  test purposes' clause.
%    \begin{macrocode}
\newcommand{\implementpurposename}{Implementation method test purposes}
\newcommand{\implementpurposehead}{%
             \sclause{\implementpurposename}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\rulepurposehead}
% \begin{macro}{\rulepurposename}
%    Command to start a `Rule violation test purposes' clause.
%    \begin{macrocode}
\newcommand{\rulepurposename}{Rule violation test purposes}
\newcommand{\rulepurposehead}{%
            \sclause{\rulepurposename}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\gtpvchead}
% \begin{macro}{\gtpvcname}
%    Command to start a `General test purposes and verdict criteria' clause.
%    \begin{macrocode}
\newcommand{\gtpvcname}{General test purposes and verdict criteria}
\newcommand{\gtpvchead}{%
            \clause{\gtpvcname}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\generalpurposehead}
% \begin{macro}{\generalpurposename}
% \begin{macro}{\generalpurposebp}
%    Commands to start a `General test purposes' clause.
%    \begin{macrocode}
\newcommand{\generalpurposename}{General test purposes}
\newcommand{\generalpurposehead}{%
            \sclause{\generalpurposename}}
\newcommand{\generalpurposebp}{%

The following are the general test purposes for this part
of ISO 10303:}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\gvcatchead}
% \begin{macro}{\gvcatcname}
% \begin{macro}{\gvcatcbp}
%    Commands to start a `General verdict criteria for all abstract test cases
%    test purposes' clause.
%    \begin{macrocode}
\newcommand{\gvcatcname}{General verdict criteria for all abstract test cases}
\newcommand{\gvcatchead}{%
  \sclause{\gvcatcname}}
\newcommand{\gvatcbp}{%

    The following verdict criteria apply to all abstract test cases
contained in this part of ISO 10303:}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\gvcprephead}
% \begin{macro}{\gvcprepname}
% \begin{macro}{\gvcprepbp}
%    Commands to start a `General verdict criteria for preprocessor 
%    abstract test cases test purposes' clause.
%    \begin{macrocode}
\newcommand{\gvcprepname}{General verdict criteria for preprocessor 
                          abstract test cases}
\newcommand{\gvcprephead}{%
  \sclause{\gvcprepname}}
\newcommand{\gvcprepbp}{%

    The following verdict criteria apply to all preprocessor 
abstract test cases contained in this part of ISO 10303:}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\gvcposthead}
% \begin{macro}{\gvcpostname}
% \begin{macro}{\gvcpostbp}
%    Commands to start a `General verdict criteria for postprocessor
%    abstract test cases test purposes' clause.
%    \begin{macrocode}
\newcommand{\gvcpostname}{General verdict criteria for postprocessor 
                          abstract test cases}
\newcommand{\gvcposthead}{%
  \sclause{\gvcpostname}}
\newcommand{\gvcpostbp}{%

    The following verdict criteria apply to all postprocessor
abstract test cases contained in this part of ISO 10303:}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\atchead}
% \begin{macro}{\atcname}
% \begin{macro}{\atcbp}
%    Commands to start a `Abstract test cases' clause.
%    \begin{macrocode}
\newcommand{\atcname}{Abstract test cases}
\newcommand{\atchead}{%
  \clause{\atcname}}
\newcommand{\atcbp}{%

    This clause specifies the abstract test cases for this part of
ISO~10303. Each abstract test case addresses one or more test
purposes from clause 4.

}
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\confclassannexhead}
% \begin{macro}{\confclassannexname}
%    Commands to start a `Conformance classes' annex.
%    \begin{macrocode}
\newcommand{\confclassannexname}{Conformance classes}
\newcommand{\confclassannexhead}{%
  \normannex{\confclassannexname}}
%    \end{macrocode}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\confclasshead}
% \begin{macro}{\confclassname}
% \begin{macro}{\confclassbp}
%    Commands to start a `Conformance class N' clause.
%    \begin{macrocode}
\newcommand{\confclassname}{Conformance class}
\newcommand{\confclasshead}[1]{%
  \sclause{\confclassname\  #1}}
\newcommand{\confclassbp}[1]{%

    To conform to conformance class #1 of ISO 10303-\theAPpartno,
an implementation must pass executable versions of the following 
abstract test cases: }
%    \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
%
%
%
% 
%
%
% \subsection{Boilerplate printing}
%
% \begin{macro}{\atsintroendbp}
%    Print boilerplate for the end of ATS introduction clause.
%    \begin{macrocode}
\newcommand{\atsintroendbp}{%


The purpose of an abstract test suite is to provide a basis for
evaluating whether a particular implementation of an application
protocol actually conforms to the requirements of that application
protocol. A standard abstract test suite helps ensure that
evaluations of conformance are conducted in a consistent manner
by different test laboratories.

This part of ISO~10303 specifies the abstract test suite for
ISO 10303-\theAPpartno, application protocol \theAPtitle.
The abstract test cases presented here are the basis for
conformance testing of implentations of ISO 10303-\theAPpartno.

\input{tsendint}
}
%    \end{macrocode}
% \end{macro}
%     Here is the text of |tsendint.tex|.
%    \begin{macrocode}
%</ats>
%<*atsf1>
    %%%% atsendint.tex  Boilerplate for end of ATS introduction clause.

    This abstract test suite is made up of two major parts:
\begin{itemize}
\item the test purposes, the specific items to be covered by
      conformance test;
\item the set of abstract test cases that meet those test purposes.
\end{itemize}

    The test purposes are statements of the application protocol
requirements that are to be addressed by the abstract test cases.
Test purposes are derived primarily from the application protocol's
AEs and AIM, as well as from other sources such as standards
referenced by the application protocol and other requirements
stated in the application protocol conformance requirements clause.

    The abstract test cases address the test purpose by:
\begin{itemize}
\item specifying the requirements for input data to be used when
      testing an implementation of the application protocol;
\item specifying the verdict criteria to be used when evaluating
      whether the implementation successfully converted the input
      data to a different form.
\end{itemize}

    The abstract test cases set the requirements for the 
executable test cases that are required to actually conduct
a conformance test. Executable test cases contain the scripts,
detailed values, and other explicit information required to
conduct a conformance test on a specific implementation of
the application protocol.

    At the time of publication of this document, conformance
testing requirements had been established for implementations
of application protocols in combination with ISO 10303-21 and
ISO 10303-22. Accordingly, this part of ISO 10303 only specifies
test purposes and abstract test cases appropriate to such
implementations. For either ISO 10303-21 or ISO 10303-22, two
kinds of implementations must be tested, preprocessors and
postprocessors. The nature of the input data and verdict
criteria are different for these two kinds of implementations.
Both are addressed in this abstract test suite.

%</atsf1>
%<*ats>
%    \end{macrocode}
%
% \begin{macro}{\atsscopebp}
%    The boilerplate for the ATS scope clause.
%    \begin{macrocode}
\newcommand{\atsscopebp}{%


    This part of ISO 10303 specifies the abstract test suite to be
used in the conformance testing of implementations of 
ISO 10303-\theAPpartno. 
The following are within the scope of this part of ISO 10303:
\begin{itemize}
\item the specification of the test purposes associated with
      ISO 10303-\theAPpartno;
\item the verdict criteria to be applied during conformance
      testing of an implementation of ISO 10303-\theAPpartno\
      using ISO 10303-21 or ISO 10303-22;
\item the abstract test cases to be used as the basis for the
      executable test cases for conformance testing.
\end{itemize}

The following are outside the scope of this part of ISO 10303:
\begin{itemize}
\item the creation of executable test cases;
\item testing other than conformance testing;
\item other implementation methods.
\end{itemize} }
%    \end{macrocode}
% \end{macro}
%
% \begin{macro}{\atspurposebp}
%    The boilerplate for the introduction to the Test purposes clause.
%    Use as: \\
%    |\atspurposebp{|\meta{comma or and}|}{|\meta{stop or other}|}{|%
%    \meta{clause number}|}|
%     where \meta{comma or and} is either a comma (,) or a comma
%    followed by the word `and' (, and); \meta{stop or other}
%    is either a full stop (.) or the end of a sentence of the
%    form (, and other sources.); and \meta{subclause number} is
%    the number of the AIM test purposes subclause.
%    \begin{macrocode}
\newcommand{\atspurposebp}[3]{%

    This clause specifies the test purposes for this part of ISO 10303.
Test purposes are derived from the information requirements contained
in clause~4 of ISO 10303-\theAPpartno#1 the AIM \Express\ schema
in annex~A of ISO 10303-\theAPpartno#2
The test purposes are organized in this clause by type.

\input{atsprpbp}

    Each AIM entity test purpose is grouped with its attribute
test purposes, all of which are contained in #3. }

%    \end{macrocode}
% \end{macro}
%
%    And here is the text of file |atsprpbp.tex|.
%
%    \begin{macrocode}
%</ats>
%<*atsf2>
    %%%% atsprpbp.tex  Some boilerplate for ATS Test purposes intro


    AE test purposes are individually identified by the prefix ``ae''
in the test purpose number. Each test purpose derived from the 
information requirements shall be interpreted as:
\begin{quotation}
    Correctly instantiate in the implementation under test the
semantic associated with the unique application concept corresponding
to {\em (insert test purpose here)} in at least one test case within
the test suite.
\end{quotation}

    AE test purposes apply to the input specifications of both
preprocessor and postprocessor test cases. AE test purposes are
derived from the AP information requirements as follows:
\begin{itemize}
\item application objects 
      (4.2 of ISO 10303-\theAPpartno). 
      A test purpose derived from an application object is a simple
      statement of the object's name. Each application object
      test purpose is documented in a separate subclause.
\item application objects with categorisations (subtypes)
      (4.2 of ISO 10303-\theAPpartno). 
      Test purposes derived from application objects with
      categorisations are statements of the application object
      name as a specific subtype.
\item application object attributes
      (4.2 of ISO 10303-\theAPpartno). 
      Test purposes derived from application object
      attributes are statements of the application object
      name with a specific attribute name.
\item application asertions
      (4.3 of ISO 10303-\theAPpartno). 
      Test purposes derived from application assertions
      are statements describing the relationship between
      two application objects. Application assertion test 
      purposes address the directions of relationships 
      as well as the number (cardinality) of relationships.
\end{itemize}

    Each application object test purpose is listed as a separate
subclause, with its related application object attribute test 
purposes. The application assertion test purposes form another
subclause.

    AIM test purposes are identified by the prefix ``aim''
in the test purpose number. Each test purpose derived from
the AIM \Express\ shall be interpreted as follows:
\begin{quotation}
Correctly instntiate in the implementation under test the
AIM element associated with the unique AIM entity corresponding
to {\em (insert test purpose here)} in at least one test case
within the test suite.
\end{quotation}

    AIM test purposes apply to the input specifications of
postprocessor test cases only. AIM test purposes are derived
directly from the expanded \Express\  listing contained in
annex~A of ISO 10303-\theAPpartno{} as follows:
\begin{itemize}
\item AIM entities. A test purpose derived from an AIM element
      is a simple statement of the entity name.
\item AIM entity attributes. Test purposes derived from AIM
      entity attributes are statements of the AIM entity with 
      a given attribute.
\end{itemize}

%</atsf2>
%<*ats>
%    \end{macrocode}
%
% \begin{macro}{\atsgtpvcbp}
%    |\atsgtpvc| --- the boilerplate for the introduction to the
%    General test purposes and verdict criteria clause.
%
%    \begin{macrocode}
\newcommand{\atsgtpvcbp}{%

    General test purposes are statements of requirements that apply
to all abstract test cases, all preprocessor abstract test cases, 
or all postprocessor abstract test cases. General verdict criteria
are the means for evaluating whether the general test purposes are 
met. General verdict criteria shall be evaluated as a part of every
executable test case to which they apply. }
%    \end{macrocode}
% \end{macro}
%
%
% \begin{macro}{\atsnoclassesbp}
%    |\atsnoclassesbp| --- the boilerplate for the Confomance class
%    annex when the AP has no conformance classes.
%    \begin{macrocode}
\newcommand{\atsnoclassesbp}{%
    Conformance to ISO 10303-\theAPpartno\ is defined only in terms
of the entire AP. Therfore, conformance requires that an 
implementation pass executable versions of all abstract 
test cases in clause 6. }
%    \end{macrocode}
% \end{macro}
%
%    The end of this package.
%    \begin{macrocode}
%</ats>
%    \end{macrocode}
%
% \begin{thebibliography}{1}
% \bibitem{ISODIR} ISO. {\em ISO Directives Part 3 -- Drafting and
%   presentation of International Standards}
% \bibitem{SD} Nigel Shaw (editor). {\em Supplementary directives for
%   the drafting and presentation of ISO~10303 (Version 2.3)}, 
%   ISO TC 184/SC4 Editing N-48, 15~March 1995.
% \bibitem{ATS} Thomas Phelps (editor). {\em Guidelines for the development
%   of abstract test suites (Version 0.96)},
%   ISO TC 184/SC4/WG6 N100b, 13~December 1995.
% \end{thebibliography}
%
% \Finale
%
\endinput

