diff options
| author | Patrick Williams <patrick@stwcx.xyz> | 2022-12-07 16:43:50 +0300 |
|---|---|---|
| committer | Patrick Williams <patrick@stwcx.xyz> | 2022-12-07 16:43:50 +0300 |
| commit | f4f2643ae8aa4a6e8f8db62a7e0377a8f222c3f9 (patch) | |
| tree | 4aa50c1dfe42dc4f1ec58dcc176f95f5d057855a /OEM_SCHEMAS.md | |
| parent | dfa3fdc3dc1045babc67ecd7974c4d997006d9c4 (diff) | |
| download | bmcweb-f4f2643ae8aa4a6e8f8db62a7e0377a8f222c3f9.tar.xz | |
markdownlint: fix all warnings
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1402cbd84c916792ca2fc0ad0f34db661cbdfa72
Diffstat (limited to 'OEM_SCHEMAS.md')
| -rw-r--r-- | OEM_SCHEMAS.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/OEM_SCHEMAS.md b/OEM_SCHEMAS.md index c30e508d3e..075809736e 100644 --- a/OEM_SCHEMAS.md +++ b/OEM_SCHEMAS.md @@ -1,4 +1,4 @@ -## Redfish OEM Resources +# Redfish OEM Resources The Redfish specification allows for OEM resources and properties to be implemented by OEMs. As a general rule, OpenBMC discourages the use of OEM @@ -6,7 +6,7 @@ namespaces in APIs. In line with this, bmcweb does not expose an API for adding OEM properties in a backward API compatible way for resources that have not been merged to master. -### Why? +## Why? OEM properties in an open source project pose many problems when compared to their closed source brethren in terms of reliability, code reuse, compatibility, @@ -40,7 +40,7 @@ and maintenance. leads to positive API design changes up front, which increases the usefulness of the code we write within the industry. -### How? +## How? If you've read the above, and still think an OEM property is warranted, please take the following steps. |