| Principles | Migration | IoT | DNS | Block Chain (e.g., OneName, NameCoin) | Distributed Hashes | Promise Theory | Ontology |
|---|
| | | SalesForce | Strong Device Identity (SDID) - Low Computing Power | SDID - High Computing Power | | | | | |
| Is there a role for a Relationship Manager? | Yes | Yes | Yes | Yes | | | | | |
| Scalable | | Reality of IoT Raw device data stream, vs. identity (asset token) | Seems Has to scalebe | Has to be | v4, v6 | | | | instances, wip rules |
| Actionable | | By the nature of the of the asset token and platform | Want it to be, brings real benefits | | Status |
|---|
| colour | YellowGreen |
|---|
| title | Partial |
|---|
|
Level of actionability will vary | IANA, Registration | | | | Defined in TBox |
| (Im)Mutable | | Depends on info available from the device | | Depending on the computing power and connectivity of the device | | Immutable/Proxy/Forwarding | | | | TBox ->'Reasoner' ->ABox |
| Contextual | | Depends on constraints of the device Nothing that excludes this | | | | | Actually provides context | | | | TBox ->'Reasoner' ->ABox |
| Transferrable (Delegation) | | As token of "agency" Need to re-mint token (new JWT) | In terms of Ownership NOT Identity Change (Change vs. Transfer) | In terms of Ownership NOT Identity Change (Change vs. Transfer) | Bought, Forwarded | | | | Ontology referentials |
| Provable | | If HoK (signed JWT via JOSE) | Requires gateway | | w/HTTPS DNSSEC | | | | Ontology referentials |
| Acknowledgable | | Allows it to be assigned, you can show this | As capable as the device is | | NMAP, other | | | | Ontology referentials |
| Revocable | | Delete the token, there is an endpoint for access token status | | | | | | | Ontology referentials |
| Constrainable | | From the device perspective - not referring to back-end | Difficult to add constraints - limited options | | Subnets, Domains, etc. | | | | Ontology referentials TBox ->'Reasoner' ->ABox |