1
0
Fork 0

Added authorization parties for all existing spec content

master
Mike Gerwitz 2013-07-31 12:58:30 -04:00
parent 281055327f
commit 14b760a1d6
3 changed files with 12 additions and 0 deletions

View File

@ -2,6 +2,8 @@
% %
% Intended to be included within its own section. % Intended to be included within its own section.
\begindeptgroup{it}
Definitions within this subsection are used most frequently by the software Definitions within this subsection are used most frequently by the software
developers addressed by this specification. developers addressed by this specification.
@ -137,3 +139,5 @@ developers addressed by this specification.
\dt{$\top$} \dt{$\top$}
Boolean value of 1; ``true''; Boolean value of 1; ``true'';
\end{description} \end{description}
\enddeptgroup

View File

@ -4,6 +4,8 @@
% %
% Also requires gls-ins-calif definition. % Also requires gls-ins-calif definition.
\begindeptgroup{uw}
For a glossary of insurance terms from the state of California, For a glossary of insurance terms from the state of California,
see~\cite{gls-ins-calif}. see~\cite{gls-ins-calif}.
@ -95,3 +97,5 @@ apply.
\end{description} \end{description}
\end{description} \end{description}
\enddeptgroup

View File

@ -2,6 +2,8 @@
% %
% Intended to be included within its own section. % Intended to be included within its own section.
\begindeptgroup{pm}
Portions of this section conform to \rfc{2119}: ``Key words for use in RFCs to Portions of this section conform to \rfc{2119}: ``Key words for use in RFCs to
Indicate Requirement Levels''. Certain terms from the RFC have been expressly Indicate Requirement Levels''. Certain terms from the RFC have been expressly
avoided; for example, the terms ``should'' and ``should not'' are not used avoided; for example, the terms ``should'' and ``should not'' are not used
@ -68,3 +70,5 @@ specification to resolve implementation issues and should exercise that ability.
\dt{\P} \dt{\P}
Paragraph reference Paragraph reference
\end{description} \end{description}
\enddeptgroup