<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bmcweb/static/redfish/v1/JsonSchemas/Message/Message.json, branch master</title>
<subtitle>OpenBMC Web server</subtitle>
<id>https://git.raptorcs.com/git/bmcweb/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/bmcweb/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/'/>
<updated>2019-10-11T21:13:05+00:00</updated>
<entry>
<title>Update Redfish schemas to 2019.2</title>
<updated>2019-10-11T21:13:05+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-10-08T18:34:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=cb103130e18689b9a8e15284f930606d512328cd'/>
<id>urn:sha1:cb103130e18689b9a8e15284f930606d512328cd</id>
<content type='text'>
Note, the DMTF changed the format of the schema file pack yet again, so
the script changes now to compensate for that.

Tested:
Ran schema validator.  One unrelated failure in LogEntry, and 4 new
warnings in PCIe devices (we're using a deprecated property).  All other
endpoints pass.

Signed-off-by: Ed Tanous &lt;ed.tanous@intel.com&gt;
Change-Id: I81c030a7c5a6a32cc12a5e7e02a9441b7891bc5d
</content>
</entry>
<entry>
<title>Update schema files to 2018.2</title>
<updated>2019-01-07T19:44:11+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-01-02T21:41:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=530520eae687a10f2fb03d2ce23ca4188b0e2440'/>
<id>urn:sha1:530520eae687a10f2fb03d2ce23ca4188b0e2440</id>
<content type='text'>
Redfish schema 2018.2 was released on September 20th, 2018.  While there
aren't any plans to utilize any of the new services, it makes sense to
keep up to date with the latest static data.

This commit was largely done automatically using the update_schemas.py
script.

Change-Id: Ieaa9f1ab2a47244ef201cfe9a064744d7d156745
Signed-off-by: Ed Tanous &lt;ed.tanous@intel.com&gt;
</content>
</entry>
<entry>
<title>Fix JsonSchema indexes</title>
<updated>2018-10-16T17:16:23+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2018-09-13T20:45:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=118b1c7102e942ace53dac9f92a954864462eebe'/>
<id>urn:sha1:118b1c7102e942ace53dac9f92a954864462eebe</id>
<content type='text'>
JsonSchema was throwing errors in the validator, so implement changes to
the update script to add the appropiate indexes.

Tested by:
Schema validator passes on the JsonSchema Fields

Change-Id: I6cb2737901b55c1089aef744d3ce3c3dfe13f17f
Signed-off-by: Ed Tanous &lt;ed.tanous@intel.com&gt;
</content>
</entry>
</feed>
