[weirds] URIs in draft-newton-et-al-weirds-rir-json-response-01

[Alex Sergeyev <[e-mail]>]

Hi,

I have a small question/proposal about weirds JSON responce format.
Mostly about "uris" section in examples from
http://tools.ietf.org/html/draft-newton-et-al-weirds-rir-json-response-01

   {
     "handle" : "XXXX-RIR",
     "startAddress" : "10.0.0.0",
     "endAddress" : "10.0.0.255",
     "ipVersion" : 4,
     "name": "NET-RTR-1",
     "description" : [ "A network used for routing" ],
     "type" : "DIRECT ALLOCATION",
     "country" : "AU",
     "parentHandle" : "YYYY-RIR",
     "remarks" : [
       "she sells seas shells",
       "down by the seashore"
     ],
     "uris" : [
       {
         "type" : "source",
         "uri" : "http://whois-rws.net/network/xxxx"
       },
       {
         "type" : "parent",
         "uri" : "http://whois-rws.net/network/yyyy"
       },
       {
         "type" : "held",
         "uri" : "http://example.net/location/xxxx"
       }
     ],
     "registrationDate" : "20110509",
     "lastChangedDate" : "20110509",
     "lastChangedBy" : "[e-mail]"
   }


In my opinion, "type" inside of each URI section is really not saying much.
Would anyone agree that automated tools would be easier to design if
say it'll be "ref" element instead. and it would refer to actual keys
inside of JSON:


   "uris" : [
       {
         "ref" : "source",
         "type": "network",
         "uri" : "http://whois-rws.net/network/xxxx"
       },
       {
         "ref" : "parentHandle",
         "type": "network",
         "uri" : "http://whois-rws.net/network/yyyy"
       },
       {
         "type" : "held",
         "ref" : null,
         "uri" : "http://example.net/location/xxxx"
       }
     ],


Something in this sense, that will allow automatic tools to make
better judgement of URIs. Also in case of contacts for domain
registrations it would be nice to do structured "refs", like ' "ref":
"contact/tech" '


I do have another note about generic "status" field for all future
JSON info responses. I'm adding it here because it makes sense if
things above are interesting.

Right now, similar to EPP in domain registration world WEIRDS will likely show:

status: ["clientTransferProhibited", "clientDeleteProhibited",
"clientUpdateProhibited"]

which in my opinion is not having value to consumer of WEIRDS info.

When I find info about domains for EPP purposes, I need to
differentiate between "clientTransferProhibited" and
"serverTransferProhibited". And I will. But, when i'm in WHOIS/WEIRDS
context, I think it's unnecessary information. My goal is to find few
basic bits of data:

"status" : {
   "transferProhibited" : true,
   "updateProhibited"  : true,
   "deleteProhibited"   : true,
   "Hold" : false
}

same thing, it'll help to add additional info URIs to those elements:

{
"ref" : "status/Hold",
"uri": ....
}

meaning that ideally you can EXTEND that status block with meaningful keys


It might be impractical for all interested parties for sure but I just
thought to start this conversation while working on toy implementation
for our own needs.


Sincerely,

Alex Sergeyev,
Dyn Labs