Example XML chunk for enum-services [IANA #171390]

Bernie, all.

From draft-ietf-enum-enumservices-guide-12, Section 5.2, below is an example of what the XML chunk could look like.

<record>
  <class>Protocol-based</class>
  <type>foo</type>
  <subtype>bar</subtype>
  <scheme>bar</scheme>
  <scheme>bars</scheme>
  <spec>
    This Enumservice indicates that the resource identified can be
    addressed by the associated URI in order to foo the bar. [...]
  </spec>
  <security>See <xref type="rfc" data="rfc9999"/>, Section 7.</security>
  <usage>COMMON</usage>
  <xref type="rfc" data="rfc9999"/>
  <xref type="person" data="John_Doe"/>
  <xref type="person" data="Jane_Dale"/>
  <info>Further information free text...</info>
</record>

<person id="John_Doe">
  <name>John Doe</name>
  <org>ACME Corp.</org>
  <uri>mailto:[email protected]</uri>
  <updated>2008-10-10</updated>
</person>
<person id="Jane_Dale">
  <name>Jane Dale</name>
  <org>ACME Corp.</org>
  <uri>mailto:[email protected]</uri>
  <updated>2008-10-10</updated>
</person>

Fields having "N/A" as value should instead simply be omitted in XML.

We did notice in the document it says "Note: You MUST NOT put email addresses in the authors field of an IANA Registration."
I would prefer a "Registrant" and a "Registrant E-mail".  Then a separate "Specification" where it points to the document and that is where a person could get the contact info for the authors.
What are your thoughts on that?  Is it possible to have the document reflect those?

Thanks,

Michelle Cotton
IANA

_______________________________________________
enum mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/enum