Changes between Initial Version and Version 1 of IMInteroperability/CommonExtensionProposal1.0

Timestamp:

08/16/13 12:16:47 (11 years ago)

Author:

Jeanne Ohren

Comment:

--

IMInteroperability/CommonExtensionProposal1.0

@@ +1 @@
+{{{
+
+I've attached an initial attempt at generalizing the gemini extensions into a more friendly measurement extension.
+
+Basically, we replace gemini:node with measurement:relation and gemini:services with measurement:services.
+
+A measurement:relation has a type (e.g. parent, child, etc.), and optional name (so we can specify a client_id), and the target_urn attribute.  The URN would be the AM that this node is the "parent" or "coordinator" for, defined by the relation type.
+
+The measurement:services gives us a way to list service type (e.g. GEMINI, GIMI, etc.) along with a descriptive name.  Each sub-element is either enable or disable.
+
+An example in rspec could look like:
+
+<measurement:relation type="parent" name="global_node" target_urn="urn:publicid:IDN+uky.emulab.net+authority+cm"/>
+
+<measurement:relation type="child" name="mp_node" target_urn="urn:publicid:IDN+uky.emulab.net+authority+cm"/>
+
+<measurement:services>
+  <measurement:enable type="GEMINI" name="passive"/>
+  <measurement:disable type="GEMINI" name="active"/>
+</measurement:services>
+
+I just whipped this up in a few minutes so suggestions/concerns are welcome.
+
+Thanks,
+- ezra 
+
+}}}
+