Added a PolicyManifestHandler.

chrome/test/data/extensions/managed_extension/schema/managed_storage.json

Index: chrome/test/data/extensions/managed_extension/schema/managed_storage.json
diff --git a/chrome/test/data/extensions/managed_extension/schema/managed_storage.json b/chrome/test/data/extensions/managed_extension/schema/managed_storage.json
new file mode 100644
index 0000000000000000000000000000000000000000..101fe2bb703b314ac0c93c72d4222e7a188310e7
--- /dev/null
+++ b/chrome/test/data/extensions/managed_extension/schema/managed_storage.json
@@ -0,0 +1,12 @@
+{
+  "$schema": "http://json-schema.org/draft-03/schema#",

[not at google - send to devlin, 2013/05/23 16:56:18]

just curious but is there any particular reason this needs to end with a #?

[Joao da Silva, 2013/05/24 21:31:49]

Yes; thanks for asking 'cause I had forgotten about it :-)

Reason 1: forward compatibility. The latest spec defines well-known $schema
constants, and this is the constant for v3. See
http://json-schema.org/latest/json-schema-core.html#anchor22.

Reason 2: this value is a valid URL that can be used to resolve a schema that
describes the schema, used for hyper-schemas. If you open this URL you'll see
that it declares its ID with this constant.

[not at google - send to devlin, 2013/05/25 00:50:57]

It would still be a a valid URL, and in fact the equivalent URL, without the #
though. It's odd to me that it's there. But the site you point out says to use
it, so, cool.

+  "type": "object",
+  "properties": {
+    "Name": {
+      "type": "string"
+    },
+    "Another": {
+      "type": "string"
+    }
+  }
+}