[Media Router] Parse device description xml in utility process

chrome/common/media_router/dial_device_description_parser.mojom

Index: chrome/common/media_router/dial_device_description_parser.mojom
diff --git a/chrome/common/media_router/dial_device_description_parser.mojom b/chrome/common/media_router/dial_device_description_parser.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..de6b17eee857b0abfbe459dd6927132c88648f84
--- /dev/null
+++ b/chrome/common/media_router/dial_device_description_parser.mojom
@@ -0,0 +1,32 @@
+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+// DIAL device description parsing interface provided by the utility process and
+// exposed by mojo policy control to the chrome browser process.
+
+module chrome.mojom;
+
+struct DialDeviceDescription {
+  // UUID (UDN).
+  string unique_id;
+
+  // Short user-friendly title.
+  string friendly_name;
+
+  // Model name.
+  string model_name;
+
+  // The reported device type, e.g. urn:dial-multiscreen-org:device:dial:1
+  string device_type;
+};
+
+interface DialDeviceDescriptionParser {
+  // Parses |device_description_xml_data| to get device description data. If
+  // parsing succeeds, invokes callback with |success| equals to true;
+  // otherwise invokes callback with |success| equals to false.
+  // |device_description|: device description object. Empty if parsing fails.

[dcheng, 2017/03/22 09:53:02]

Is it possible to link to some sort of spec for the device description? It'd be
useful to know what it's supposed to look like.

[zhaobin, 2017/03/22 19:18:52]

Done.

+  ParseDialDeviceDescription(string device_description_xml_data)
+      => (bool success,
+          DialDeviceDescription? device_description);
+};