WHOIS fields translated to semantic

Question

There are a lot of "good" WHOIS interpreters, like python-whois or phpWhois, but each has its own interpretation of the fields and use different JSON fields and JSON structures...

I am looking for a "Rosetta Stone" semantic tool... It exists? Any sematic jargon as SchemaOrg or free RDF/JSON-LD/etc. interpretion, mapping fields of the raw whois file into its semantic.

Exemples of most frequent semantic usage, and its fieldName-to-Semantic mapping:

WHOIS field domain is wikidata/Q32635 or uri4uri/Domain.
WHOIS field owner is schemaOrg/Organization's name.
WHOIS field ownerid is is schemaOrg/Organization's vatID.
WHOIS field country is schemaOrg/Country's addressCountry.
... The question is: where the another mappings? where I find (or how to use) all the WHOIS fields?

PS: some of the "most frequent usage" semantic like WHOIS field owner, registrar and domain are de facto standards, others no... The specific standards exists (!) in the context of the registrar, so, the cited tools (eg. phpWhois's whois.*.php) do the final interpretation, and this is the "Roseta's" locus of interpretation.

score 0 · Answer 1 · answered May 02 '16 at 15:43

0

There is no "Rosetta stone". The WHOIS protocol specification traditionally never provided any recommendation or guideline about what data should be disclosed, or which format should be used.

Therefore, any registry can virtually return a different response format and representation.

answered May 02 '16 at 15:43

Simone Carletti

173,507
49
363
364

Hum... Sorry, I edited with better explanation, can you check? Now the concept of "most frequent semantic usage" is in bold, and the PS explains that specific "*registrar* Roseta" of each country is in fact the source of the mapping, that each tool do (each tool in a better or worse way). – Peter Krauss May 02 '16 at 15:57

score 0 · Answer 2 · edited Oct 07 '21 at 13:33

Homework report.

There are no "standard Rosetta stone"

No standard, of course: the current RFC 3912 WHOIS protocol specification say nothing...

It is, since 2004, a classic and well-documented problem of Internet. See this SAC-051 ICANN 2011 report, or Wikipedia, or this 2012 blog.

The new standard that replaced WHOIS!

What??!?

RDAP is a successor protocol to the very old WHOIS protocol.
RFC 7480

... But, as asked here, How to successfully use RDAP protocol instead of whois , there are no "working RDAP". So, meanwhile: we need WHOIS and a Rossetta for it!

There are some "try to Rosetta"

As I cited, some APIs (python-whois, phpWhois, and others), do good job, they translated all TXT key-value pairs of all Internet top-level domain authorities... Need only a next step translation, that is a semantic indicator for each key.

When these API projects was developed, anyone heard of RDAP... But now, 2016, RDAP can be used as a reference to fix a standard JSON for WHOIS APIs.

As of 2019-08-26 RDAP is mandatory, by ICANN, for all gTLD registries and registrars. — Patrick Mevzek, Mar 10 '20 at 15:39

WHOIS fields translated to semantic

2 Answers2

There are no "standard Rosetta stone"

The new standard that replaced WHOIS!

There are some "try to Rosetta"

Linked