Re: [EPP-discuss] Draft EPP Specification rev. 1.0 and invitation to meeting/workshop

From: Jens Wagner <jwagner_at_hexonet.net>
Date: Thu, 01 Nov 2012 15:14:14 +0100

Hi Teddy,

according to your XSD below, I think the request XML should look like that:

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
        <command>
                <create>
                        <host:create xmlns:host="urn:ietf:params:xml:ns:host-1.0" xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0 host-1.0.xsd">
                                <host:name>ns2.eriktester.dk</host:name>
                                <host:addr ip="v4">127.0.0.1</host:addr>
                                <host:addr ip="v6">0:0:0:0:0:0:0:1</host:addr>
                        </host:create>
                </create>
                <extension>
                        <dkhm-host:create xmlns:dkhm-host="urn:dkhm:params:xml:ns:dkhm-host-1.0" xsi:schemaLocation="urn:dkhm:params:xml:ns:dkhm-host-1.0 dkhm-host-1.0.xsd">
                                <dkhm-host:responsible>TEST1234-DK</dkhm-host:responsible>
                        </dkhm-host:create>
                 </extension>
                <clTRID>6d5367c0ac54b1be06d60e385866f8c9</clTRID>
        </command>
</epp>


Best,
- jens


On 01.11.2012 14:23, Jonas B. Nielsen wrote:
> Hi Teddy and others,
>
> Thanks for your very insightful response. I have changed our XSD implementation to reflect your suggestions, I have however run into some minor issues.
>
> If you take an example of creating a host object:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
> <command>
> <create>
> <host:create xmlns:host="urn:ietf:params:xml:ns:host-1.0" xsi:schemaLocation="urn:ietf:params:xml:ns:host-1.0 host-1.0.xsd">
> <host:name>ns2.eriktester.dk</host:name>
> <host:addr ip="v4">127.0.0.1</host:addr>
> <host:addr ip="v6">0:0:0:0:0:0:0:1</host:addr>
> </host:create>
> </create>
> <extension>
> <dkhm-host:responsible xmlns:dkhm-host="urn:dkhm:params:xml:ns:dkhm-host-1.0" xsi:schemaLocation="urn:dkhm:params:xml:ns:dkhm-host-1.0 dkhm-host-1.0.xsd">TEST1234-DK</dkhm-host:responsible>
> </extension>
> <clTRID>6d5367c0ac54b1be06d60e385866f8c9</clTRID>
> </command>
> </epp>
>
> Our extension is the dkhm-host:responsible specified in the extension segment.
>
> In your own (dkhm-host-1.0.xsd), do you specify a createType or do you specify and extension. I have seen examples of both, but our validator keeps complaining about the dkhm-host:responsible object.
>
> XML parsing failed xmlns:dkhm-host: 'urn:dkhm:params:xml:ns:dkhm-host-1.0 xsi:schemaLocation="urn:dkhm:params:xml:ns:dkhm-host-1.0 dkhm-host-1.0.xsd"' is not a valid URI
>
> But it might be my URI specifications which are not sufficiently explicit.
>
> Currently my XSD look as follows:
>
> <?xml version="1.0" encoding="utf-8"?>
> <schema targetNamespace="urn:dkhm:params:xml:ns:dkhm-host-1.0"
> xmlns:dkhm-host="urn:dkhm:params:xml:ns:dkhm-host-1.0"
> xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
> xmlns="http://www.w3.org/2001/XMLSchema"
> elementFormDefault="qualified">
> <!--
> Import common element types.
> -->
> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" schemaLocation="eppcom-1.0.xsd" />
> <annotation>
> <documentation>Extensible Provisioning Protocol v1.0 host provisioning schema. DKHM extension v1.0</documentation>
> </annotation>
> <!--
> Child elements found in EPP commands.
> -->
> <element name="create" type="dkhm-host:createType" />
>
> <!--<element name="extension">
> <complexType>
> <choice>
> <element name="responsible" type="dkhm-host:responsible" minOccurs="1" maxOccurs="1" />
> </choice> </complexType>
> </element>-->
>
> <!--
> Utility types.
> -->
> <simpleType name="responsible">
> <restriction base="eppcom:clIDType"></restriction>
> </simpleType>
> <!--
> Child elements of the <create> command.
> -->
> <complexType name="createType">
> <sequence>
> <element name="responsible" type="dkhm-host:responsible" minOccurs="1" maxOccurs="1" />
> </sequence>
> </complexType>
> <!--
> End of schema.
> -->
> </schema>
>
> jonasbn
>
> On 26/10/2012, at 15.11, Teddy Hogeborn <teddy.h+dk-epp_at_nmugroup.com> wrote:
>
>> "Jonas B. Nielsen" <jonasbn_at_dk-hostmaster.dk> writes:
>>
>>> On 26/10/2012, at 14.29, Patrik Fältström <paf_at_frobbit.se> wrote:
>> [...]
>>>> - The response with tracking number for create domains must be
>>>> machine parseable. What is proposed today is not good enough.
>> I agree with Patrik.
>>
>>> Due to an implementation issue I had to roll-back to a simpler
>>> implementation, the initial proposal, which we still aim for looks
>>> some like this:
>>>
>>> <?xml version="1.0" encoding="utf-8" standalone="no"?>
>>> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
>>> <response>
>>>
>>> <result code="1001">
>>> <msg>Create domain domain.dk pending. Sequence ID = 2468.</msg>
>>> </result>
>>> <resData>
>>> <trackingNo>1234</trackingNo>
>>> </resData>
>>> <msgQ count="2" id="ABC-1234-XY"></msgQ>
>>> <trID>
>>> <clTRID>300c8288dbe6e15e837733983143e63d</clTRID>
>>> <svTRID>5B1D5990-0988-11E2-A187-AFB5A63584A5</svTRID>
>>> </trID>
>>> </response>
>>> </epp>
>> That's not RFC compliant. What you should do is something like this:
>>
>> <response>
>> [...]
>> <trID>
>> <!-- This is just a suggestion -->
>> <svTRID>DK-TRACKINGNO-1234</svTRID>
>> </trID>
>> <extension>
>> <!-- This is what you REALLY should do -->
>> <trackingno xmlns="urn:dk:dk-hostmaster:epp:dk-1.0">1234</trackingno>
>> </extension>
>> </response>
>>
>> /Teddy Hogeborn
>>
>> --
>> System Administrator at Nordisk Media Utveckling AB
>> https://www.nmugroup.com/ tel:+46.40304770
>>
> --
> Med venlig hilsen/Best Regards
> Jonas B. Nielsen
> Software udvikler/Softwaredeveloper
>
> DK Hostmaster A/S
> Kalvebod Brygge 45, 3. sal
> 1560 København V
>
> Tlf. +45 33 64 60 60
> Mobil: +45 31 54 60 56
> Fax.: +45 33 64 60 66
> Email: jonasbn_at_dk-hostmaster.dk
> Homepage: https://www.dk-hostmaster.dk
>
> .dk Danmarks plads på Internettet
>
> -------------------------------------------------------------------------
> Dette er en e-mail fra DK Hostmaster A/S. Denne e-mail kan indeholde
> fortrolig information, som kun er til brug for den tiltænkte modtager.
> Hvis du ved en fejl har modtaget denne e-mail, bedes du venligst straks
> give afsenderen besked om dette og slette e-mailen fra dit system uden
> at offentliggøre, videresende eller tage kopi af meddelelsen.
>
> This is an email from DK Hostmaster A/S. This message may contain
> confidential information and is intended solely for the use of the
> intended addressee. If you are not the intended addressee please notify
> the sender immediately and delete this e-mail from your system. You are
> not permitted to disclose, distribute or copy the information in this
> e-mail.
> --------------------------------------------------------------------------
>
>

-- 
Jens Wagner
Chief Executive Officer
HEXONET GmbH
T: +49 6841 69 84 0
F: +49 6841 69 84 199
E:jwagner_at_hexonet.net
W:http://www.hexonet.net
HEXONET GmbH, Talstrasse 27, 66424 Homburg, Germany.  CEO & General Manager: Jens Wagner, HRB 2839 (HOM), Amtsgericht Saarbrücken, VAT-ID: DE-138316882
HEXONET Services Inc., #104 - 7455 132nd Street, Surrey, B.C., V3W 1J8, Canada.  CSO & General Manager: Robert Birkner
This email and any files transmitted are confidential and intended only or the person(s) directly addressed. If you are not the intended recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete this email with any files that may be attached.
Received on Thu Nov 01 2012 - 15:14:14 CET

This archive was generated by hypermail 2.3.0 : Fri Feb 06 2015 - 11:39:05 CET