[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: ietf-provreg@cafax.se
From: Klaus Malorny <Klaus.Malorny@knipp.de>
Date: Wed, 05 Oct 2005 12:26:25 +0200
Sender: owner-ietf-provreg@cafax.se
User-Agent: Thunderbird 1.4 (Windows/20050908)
Subject: [ietf-provreg] registries, XML & EPP (again)

Hi all,

digging deeper into the EURid EPP specs I discovered something that is in my 
humble opinion a bit more serious than the prefix problem. It looks like that 
they took the XML schema files of the domain and contact objects (RFC 3731, 
3733) and deliberately modified them, like adding a new contact type or changing 
whether elements are mandatory or not. I am not completely aware of all changes, 
as the schema files are not available yet. While the changes themselves are not 
a problem at all, EURid still associates these new schemes with the IETF 
namespaces, namely urn:ietf:params:xml:ns:contact-1.0 and 
urn:ietf:params:xml:ns:domain-1.0. Isn't this something that should really be 
avoided for the sake of the clarity and compatibility? Technically, it is not a 
problem to use any other URI, like they did for their proprietary extensions anyway.

Please don't misunderstand me, I do not want to start an EURid or whatever 
registry bashing here, but the least what we need is a standard that isn't one 
(for whatever reason). Lessons like SQL or HTML have shown where something can end.



      |       |
      | knipp |                   Knipp  Medien und Kommunikation GmbH
       -------                           Technologiepark
                                         Martin-Schmeißer-Weg 9
      Dipl. Inf. Klaus Malorny           44227 Dortmund
      Klaus.Malorny@knipp.de             Tel. +49 231 9703 0

Home | Date list | Subject list