For Clarification - you have to remember that many of these response codes
are what is sent from the registry (RRP Protocol) - we can only extend the
level of detail to you that is extended to us...
By default an order has "Contact", and "Billing" with an optional
"Technical" contact that the end user can fill in. "Technical" is parsed
from the Reseller Web Interface (if that is what you desire), and *by
default* "Contact" is extended into "Owner/Org" (a.k.a. Registrant) and
"Admin" contact information.
The definitions have already been discussed numerous times in these lists
(available in the archives) - and you can also read ICANN documentation on
this topic as well.
If you wish to extend your business model to allow your clients the
ability to differentiate between "Owner" and "Admin", you can alter the
code to request that information - by default (codebase we provide based
on API) things work as described above.
I personally agree that examples in the codebase should not be written in
Perl - the simple fact is our team IS a bunch of Perl programmers, and
this is what they do best. I'm not familiar enough with languages to know
how to describe a "perl hash" in either psuedocode or another language.
I'm sure many of you here could.
The API in its current state is leaps and bounds further than any other
"API" (and I that's extending the definition a little bit) previously
released - things WILL get better. This is the first step - a much more
comprehensive document set.
Charles Daminato
OpenSRS Support Manager
[EMAIL PROTECTED]
On Fri, 1 Sep 2000, Neil H. wrote:
> Clarification please:
>
> Why are there 12 different descriptions for a response code? Aren't there
> enough numbers in the world (an infinite amount) that OpenSRS could give
> each response its own unique code? This is pure laziness guys. There is no
> other excuse and if there is I would like to hear it.
>
> Second,
> I think this is a general "registrar" question. I think it is very
> unclear what is each role of a contact. In the open srs manual order form
> (and I Haven't been able to implement anything else :) ) There is Contact,
> Billing and Technical. In the new release on page 39 we now have references
> to Owner, Admin, Tech, Billing. I think some clarification is due here? I
> would appreciate some definition of each role.
>
> This is it for now. I feel I am being harsh and critical but I am only one
> person not a team. One more thing I just remembered that I wanted to
> mention is that no matter how much OPEN opensrs is if you know PERL you are
> like way ahead of the game. The constant references to Perl in the Appendix
> A is bad. I mean please reference some other language just some variety.
> You guys are all perl developers and that is fine, but make it a little less
> obvious and a little more open and I think everyone will be happier.
>
> Well my 2 cents for now. If I get the time I will continue to scrutinize
> this document, but I think I have made a few points in the past two
> messages. And please no hard feelings I love the service at opensrs and the
> availablility of the UK domains is an added delight. In my opinion being
> critical like this will help us all.
>
> Thanks,
>
> Neil
>
>
>
