diff --git a/spec/016_cic_token_platform_registration.md b/spec/016_cic_token_platform_registration.md
index eb88d0f..be4c98a 100644
--- a/spec/016_cic_token_platform_registration.md
+++ b/spec/016_cic_token_platform_registration.md
@@ -19,10 +19,19 @@ A separate, more formal document will be written as a request for comment for de
 
 The `DecentralizedStorageResolver` contract facilitates multiplexing of data resource locations across web2 and web3 networks. It is a separately maintained project with its own documentation. Its utility here is to let an entity specify one or more locations where the metadata for the registration can be retrieved.
 
-The `CICRegistration` contract announces the availability of metadata for a given token. In essence it is a simple chain of mappings:
+The `CICRegistration` contract announces the availability of metadata for a given token. In essence it is a simple chain of mappings (names do not match contract properties):
 
 ```
-token_address -> token_announcer_address -> resolver_address -> resolver_type -> resolver_chain
+{
+	'token_address': {
+		'token_announcer_address': {
+			'resolver_address': <address>,
+			'resolver_type': <bytes32>,
+			'resolver_chain': <bytes32>,
+		}
+	}
+}
+
 ```
 
 The `resolver_type` is a sha256 hash of a custom resolver id. The only three recognized values at current time are: