[Ietf-not43] From answer to domain

[David Blacka]

On Wednesday, October 15, 2003, at 01:08  PM, Chris Ambler wrote:

> 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?

I might be misunderstanding this whole conversation, but it seems to me 
that you are trying to use the IRIS/DREG1 schema for some 
non-IRIS/DREG1 purpose, and that you are having some difficulties 
because of this.

Is the goal to create a WHOIS interchange format that will interoperate 
with CRISP, or is this an independent effort?  (By interoperate, I am 
thinking that there may be a desire for a registrar to use one of these 
files as the data source for an IRIS/DREG1 server).

If this is an independent effort, then you should just be using the 
DREG1 schema as a starting point.  The DREG1 schema was designed in the 
context of the IRIS architecture.  If that architecture isn't there, 
then the schema isn't going to be ideal.  In that case, you may as well 
as create your own (albeit similar) schema.

If it isn't an independent effort, then we need to make sure we 
understand how your efforts and IRIS need to interoperate.  The schemas 
are not set in stone, but we need to understand the problems before we 
can judge what changes (if any) need to be made to the schemas.

--
David Blacka    <davidb at verisignlabs.com>
Sr. Engineer    Verisign Applied Research