[Ietf-not43] From answer to domain

[Chris Ambler]

><domain> is a derivation of <result>.
>
>Keep in mind that xsd's are only the formal definition of the schema. 
>Implementations are free to use other validation methods so long as they 
>accomplish the same task.

Ah, that makes more sense.

So, in the XSD, it is codified that the Item element of the answer element,
being of type resultType, may be serialized as a simpleEntityType,
limitsType or serviceIdentificationType. I added the allowance such that it
could also be serialized as a domainType, and all works well.

Now, let's make sure I have this clear:

Once I fill in the domain element with all of my entities, I then put the
actual elements that the entities reference in the additional element,
ensuring that the entityName fields match. Correct?

Heretical question: if the XSD is just a suggestion, as you intimate, what
prevents me from breaking normalization and adding the allowance that, for
example, the technicalContacts element of the domain element may contain, in
addition to an iris:entity element, a contact element?

Okay, let's say I don't do that (because your objection will be, "yes, that
breaks normalization, and we'd prefer that not happen), but put the actual
element in the additional element... is there a procedure whereby I can push
my XSD back out as the "official XSD for using the dreg:domain inside of an
answer element for the purpose of registrar WHOIS transmission?" or some
such?

The goal being to publish that XSD as well as my sample code when we're all
done so other registrars can participate (yes, I just got the OK from eNom
to push the code and spec for this out into the public once it's working).

Christopher