[sbml-svn] SF.net SVN: sbml:[22311] trunk/specifications/sbml-level-3/version-2/comp/ spec/intro.tex

[<luc...@us...>]

Revision: 22311
          http://sourceforge.net/p/sbml/code/22311
Author:   luciansmith
Date:     2015-06-25 16:24:55 +0000 (Thu, 25 Jun 2015)
Log Message:
-----------
Missing 'of'; noticed by Robert Muetzelfeldt.

Modified Paths:
--------------
    trunk/specifications/sbml-level-3/version-2/comp/spec/intro.tex

Modified: trunk/specifications/sbml-level-3/version-2/comp/spec/intro.tex
===================================================================
--- trunk/specifications/sbml-level-3/version-2/comp/spec/intro.tex	2015-06-25 07:13:10 UTC (rev 22310)
+++ trunk/specifications/sbml-level-3/version-2/comp/spec/intro.tex	2015-06-25 16:24:55 UTC (rev 22311)
@@ -15,7 +15,7 @@
   \label{fig1}
 \end{figure}
 
-The effort to create a hierarchical model composition mechanism in SBML has a long history, which we summarize in \sec{background}.  It has also been known by different names.  In the beginning, it was called \emph{modularity} because it allows a model to be divided into structural and conceptual modules.  It was renamed \emph{model   composition} when it became apparent that the name ``modularity'' was easily confused with other notions modularity, particularly XHTML~1.1~\citep{xhtml} modularity, which concerns decomposition into separate files.  To make clear that the purpose is structural \emph{model} composition, regardless of whether the components are stored in separate files, the SBML community adopted the name SBML \emph{Hierarchical Model Composition}.
+The effort to create a hierarchical model composition mechanism in SBML has a long history, which we summarize in \sec{background}.  It has also been known by different names.  In the beginning, it was called \emph{modularity} because it allows a model to be divided into structural and conceptual modules.  It was renamed \emph{model   composition} when it became apparent that the name ``modularity'' was easily confused with other notions of modularity, particularly XHTML~1.1~\citep{xhtml} modularity, which concerns decomposition into separate files.  To make clear that the purpose is structural \emph{model} composition, regardless of whether the components are stored in separate files, the SBML community adopted the name SBML \emph{Hierarchical Model Composition}.
 
 To support a variety of composition scenarios, this package provides for optional black-box encapsulation by means of defined data communication interfaces (here called \emph{ports}).  In addition, it also separates model \emph{definitions} (i.e., blueprints, or templates) from \emph{instances} of those definitions, it supports optional external file storage, and it allows recursive model decomposition with arbitrary submodel nesting.