diff options
| author | rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-02-26 03:20:46 +0000 |
|---|---|---|
| committer | rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-02-26 03:20:46 +0000 |
| commit | b789c0ab2ffca627f908765bb34408b5f3f89d85 (patch) | |
| tree | a544bb74bd1c36831605337e83cddabd0e37d728 /commands.tex | |
| parent | 86e4e22fcb381dcb8cd9a795b527676b4d46e577 (diff) | |
Feedback: add normative marker.
From http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html:
Normative statements MUST be referenceable so that a statement may be
referenced from another part of a specification, but more importantly
so they can be referenced from Conformance Clauses.
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@265 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
Diffstat (limited to 'commands.tex')
| -rw-r--r-- | commands.tex | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/commands.tex b/commands.tex index 671757b..c4b19de 100644 --- a/commands.tex +++ b/commands.tex @@ -8,3 +8,7 @@ % How we format a field name \newcommand{\field}[1]{\emph{#1}} + +% Mark a normative paragraph (driver or device) +\newcommand{\drivernormative}[1]{\phantomsection\label{drivernormative:#1}} +\newcommand{\devicenormative}[1]{\phantomsection\label{devicenormative:#1}} |