Make OpenRMC spec compatible with tcg-pandoc.

To build:

First clone [ocp-spec-tools](https://github.com/opencomputeproject/ocp-spec-tools/), and then run:

```
$ path/to/ocp-spec-tools/ocp-docker-pull.sh
$ path/to/ocp-spec-tools/ocp-docker-run.sh --pdf OpenRMC_UsageGuide_v1.2.pdf OpenRMC_UsageGuide_v1.2.ocp
```

The following metadata fields are not currently respected by ocp-spec-tools:

 - `supersedes`
 - `status`
 - `released`
 - `class`
 - `copyright`
 - `paragraph_numbering`

Signed-off-by: Jeff Andersen <jeffandersen@google.com>

Author: bluegate010

RackManager/OpenRMC_UsageGuide_v1.2.bibliography.yaml

@@ -0,0 +1,21 @@
+references:
+  - id: "openrmc-design-specification"
+    title: "OpenRMC Design Specification"
+    publisher: "Open Compute Project"
+    url: "http://www.opencompute.org"
+  - id: "ocp-baseline-hw-management-profile"
+    title: "Usage Guide and Requirements for the OCP Baseline Hardware Management Profile v1.0.1"
+    publisher: "Open Compute Project"
+    url: "https://www.opencompute.org/documents/usage-guide-for-baseline-hw-mgmt-api-v1-0-1-final-pdf"
+  - id: redfish-firmware-update
+    title: "Redfish Firmware Update White Paper"
+    publisher: "Distributed Management Task Force"
+    url: "https://www.dmtf.org/sites/default/files/standards/documents/DSP2062_1.0.0.pdf"
+  - id: redfish-api-specification
+    title: "Redfish API Specification"
+    publisher: "Distributed Management Task Force"
+    url: "https://www.dmtf.org/dsp/DSP0266"
+  - id: redfish-certificate-whitepaper
+    title: "Redfish Certificate Whitepaper"
+    publisher: "Distributed Management Task Force"
+    url: "https://www.dmtf.org/sites/default/files/standards/documents/DSP2059_1.1.0.pdf"

RackManager/OpenRMC_UsageGuide_v1.2.dsp.cfg

@@ -1,3 +1,23 @@
+---
+project: Hardware Management
+title: Usage Guide for Rack Management
+version: 1.2.0
+supersedes: 1.1.0
+status: draft
+released: true
+class: info
+date: 2025-03-20
+copyright: 2023-2025
+paragraph_numbering: no
+bibliography: OpenRMC_UsageGuide_v1.2.bibliography.yaml
+...
+
+---
+
+\tableofcontents
+
+---
+
 # License
 
 This work is licensed under a [Creative Commons Attribution-ShareAlike
@@ -116,7 +136,7 @@ The response contains the following fragment. The fragment shows the URI for the
 
 The fragment shows two actions that can be perform on an aggregate, either temporary or persistent.
 The action is invoke by performing a POST to the URI contained in Target property.
-The contents of the request body in desribed in resource whose URI is contained in the @Redfish.ActionInfo property.
+The contents of the request body in desribed in resource whose URI is contained in the \@Redfish.ActionInfo property.
 
 ```
     {
@@ -133,19 +153,19 @@ The contents of the request body in desribed in resource whose URI is contained
         "Actions": {
             "#AggregationService.Reset": {
                 "target": "/redfish/v1/AggregationService/Actions/AggregationService.Reset",
-                "@Redfish.ActionInfo": "/redfish/v1/AggregationService/ResetActionInfo"
+                "\@Redfish.ActionInfo": "/redfish/v1/AggregationService/ResetActionInfo"
             },
             "#AggregationService.SetDefaultBootOrder": {
                 "target": "/redfish/v1/AggregationService/Actions/AggregationService.SetDefaultBootOrder",
-                "@Redfish.ActionInfo": "/redfish/v1/AggregationService/SetDefaultBootOrderActionInfo"
+                "\@Redfish.ActionInfo": "/redfish/v1/AggregationService/SetDefaultBootOrderActionInfo"
             }
         }
     }
 ```
 
 ## Update Firmware
 
-The firmware can be updated with a pull or push method. The "Redfish Firmware Update Whitepaper"\[3\] has detail discussion of the firmware update process.
+The firmware can be updated with a pull or push method. The "Redfish Firmware Update Whitepaper" [@{redfish-firmware-update}] has detail discussion of the firmware update process.
 
 The main process is for the firmware package to be delivered opaquely, and the Redfish Service interprets the firmware package to determine the components that are updated.
 The Targets property can be used to guide and constrain this behavior.
@@ -752,7 +772,7 @@ To perform a reset of the group, a POST is invoked to the value of the Target pr
   POST /redfish/v1/AggregationService/Actions/Aggregate.Reset
 
 The POST request shall contain a request body. The contents of the request body are described by resource specified by the
-@Reddfish.ActionInfo property. The TargetURIs property specifies the group to be used.
+\@Reddfish.ActionInfo property. The TargetURIs property specifies the group to be used.
 After the group is used, it is forgotten.
 
 ```
@@ -1109,7 +1129,7 @@ it.
 - **Managed Node List =** Node Certificate + Time Stamp of Initial
   session establishment
 
-> In the Redfish Certificate Management Whitepaper \[1\], the node
+> In the Redfish Certificate Management Whitepaper [@{redfish-certificate-whitepaper}], the node
 > certificate and rack manager certificate are referred to as device
 > identity certificates.
 
@@ -1247,18 +1267,6 @@ Reason for Classification
 |  |  |  |  |  | Other node managers do not have node’s token (encrypted during transit) |
 | 9 | A rogue rack manager attempts to reply legitimate encrypted rack manager’s token | Network Adversary | End User’s Data | H | In discovery flow, node decrypts rack manager’s token and checks the cert in token with the cert that rogue rack manager passes down early in discovery flow. Discrepancy leads to the fact that node logs “Suspicious Node Manger” event (no session will get establish). |
 
-# References
-
-\[1\] "[OpenRMC Design Specification](http://www.opencompute.org/)"
-
-\[2\] Usage Guide and Requirements for the OCP Baseline Hardware Management Profile v1.0.1
-
-\[3\] "[Redfish Firmware Update White Paper](https://www.dmtf.org/sites/default/files/standards/documents/DSP2062_1.0.0.pdf)"
-
-\[4\] "[Redfish API Specification](https://www.dmtf.org/dsp/DSP0266)"
-
-\[5\] "[Redfish Certificate Whitepaper](https://www.dmtf.org/sites/default/files/standards/documents/DSP2059_1.1.0.pdf)"
-
 # Revision 
 
 | Revision/Version | Date | Description |