§ Hologram.zone specs v1.0

Specification Status: Pre-Draft

Latest Draft: 2060-io.github.io/hologram.zone-specs/

Editors:
Fabrice Rochette (2060.io)
Participate:

GitHub repo

File a bug

Commit history

§ About this Document

This document provides all the required information for:

§ Introduction

§ What is Hologram?

This section is non-normative.

Hologram is a Verifiable Credential wallet and messaging app with true privacy preserving features. Unlike other messaging apps, Hologram is a self-custody app, which means user’s data is only stored on device, and exclusively under user’s control.

Hologram is available in the main app stores, look for “Hologram Messaging” in apple store, google play or huawei’s app gallery.

§ Why an hologram.zone website?

This section is non-normative.

This mini website is required to handle end-user fallback actions, such as when a user scans an hologram service QR, or click an hologram link, but Hologram app is not installed in user’s handset.

§ Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative. The key words MAY, MUST, MUST NOT, OPTIONAL, RECOMMENDED, REQUIRED, SHOULD, and SHOULD NOT in this document are to be interpreted as described in BCP 14 RFC2119 RFC8174 when, and only when, they appear in all capitals, as shown here.

§ Logic

This section is non-normative.

Look at these 2 use cases:

In both case we are talking about the same URL. This URL is always be formatted as follows:

https://hologram.zone/?oob=QIUiudggiUQ..&tp=ABC

or

https://hologram.zone/?_oob=QIUiudggiUQ..&tp=ABC

where:

§ About Smart App Banner

This section is non normative.

A Smart App Banner is a banner that is shown it the top of the page, above the content, that detects if a app is already installed or not.

It is straightforward for iOS/safari but not for other browsers/os combination.

For more information:

§ About App store detection

This section is non normative.

Hologram is available in Google Play, Huawei App Gallery, and Apple Store.

In mobile environment, it is important to find the best way to properly detect which stor(s)) should we present to the user.

For detecting which app store the user should download from, you can use use the user agent for detecting if iOS or Android.

For Android, you could detect the app store using the following:

https://forums.developer.huawei.com/forumPortal/en/topic/0204421140621710058

If detection is not a 100% sure, show all possible options to user.

Based on the detection:

§ Hologram app is already installed on user’s handset

https://hologram.zone/?oob… or https://hologram.zone/?_oob…:

uml diagram

https://hologram.zone/:

uml diagram

get or install

§ Hologram app is not installed on user’s handset

In this case, because OS cannot find a registered App for the URL starting with https://hologram.zone?oob=…, browser loads the URL. Smart App Banner SHOULD be rendered.

hologram.zone website MUST show a content to the user so that the following flow can be performed by the user:

uml diagram

§ Pages

The website MUST have 2 pages.

§ [PAGE-MAIN-1] Case #1: when user arrive spontaneously in website (no DTS invitation in URL), mobile phone

User was directed to https://hologram.zone/.

Illustration:

alt text

figma

§ [PAGE-MAIN-2] When user arrive spontaneously in website (no DTS invitation in URL), desktop or tablet

User was directed to https://hologram.zone/.

The website MUST show:

alt text

figma

§ [PAGE-MAIN-3] User arrives with a DTS invitation in URL, from a mobile phone

User was directed to https://hologram.zone/?oob=QIUiudggiUQ..&tp=ABC

Illustration:

alt text

figma

§ [PAGE-MAIN-4] User arrives with a DTS invitation in URL, desktop or tablet

User was directed to https://hologram.zone/?oob=QIUiudggiUQ..&tp=ABC

alt text

figma

§ [PAGE-TYC] Terms and Conditions and Privacy Policy.

Sample Content (in english):

§ Getting service name and icon

To be able to render the service name and icon, we MUST try to get the label and imageUrl attributes in the oob or _oob parameter. First, we need to decode its base64.

Example:

eyJAdHlwZSI6Imh0dHBzOi8vZGlkY29tbS5vcmcvb3V0LW9mLWJhbmQvMS4xL2ludml0YXRpb24iLCJAaWQiOiJkOWRlMTU5Yy0zNTk5LTQ5ZDAtOGQ0Zi0zZjY5NTAzYzc3MjMiLCJsYWJlbCI6IkRlbW8gQ2hhdGJvdCBBZ2VudCIsImFjY2VwdCI6WyJkaWRjb21tL2FpcDEiLCJkaWRjb21tL2FpcDI7ZW52PXJmYzE5Il0sImhhbmRzaGFrZV9wcm90b2NvbHMiOlsiaHR0cHM6Ly9kaWRjb21tLm9yZy9kaWRleGNoYW5nZS8xLjEiLCJodHRwczovL2RpZGNvbW0ub3JnL2Nvbm5lY3Rpb25zLzEuMCJdLCJzZXJ2aWNlcyI6WyJkaWQ6d2ViOmNoYXRib3QtZGVtby5kZXYuMjA2MC5pbyJdLCJpbWFnZVVybCI6Imh0dHBzOi8vZC5jaGF0Ym90LWRlbW8uZGV2LjIwNjAuaW8vYXZhdGFyLnBuZyJ9

will be decoded to:

{
   "@type":"https://didcomm.org/out-of-band/1.1/invitation",
   "@id":"d9de159c-3599-49d0-8d4f-3f69503c7723",
   "label":"Demo Chatbot Agent",
   "accept":[
      "didcomm/aip1",
      "didcomm/aip2;env=rfc19"
   ],
   "handshake_protocols":[
      "https://didcomm.org/didexchange/1.1",
      "https://didcomm.org/connections/1.0"
   ],
   "services":[
      "did:web:chatbot-demo.dev.2060.io"
   ],
   "imageUrl":"https://d.chatbot-demo.dev.2060.io/avatar.png"
}

§ If oob message has “@type”:“https://didcomm.org/out-of-band/1.1/invitation” attribute

Extract the info like this:

§ If oob message has “type”: “https://didcomm.org/out-of-band/2.0/invitation” attribute

At the moment, the page MUST just show the link to connect, saying “continue to service”, as name and imageUrl cannot be extracted.

§ Show found information on screen

Based on the information it was possible to get, the maximum possible info MUST be shown.

§ Internationalization

Website MUST detect browser’s language and render the website in the language of the browser if possible, else MUST fallback to english.

Texts and other internationalizable elements MUST be in a directory/files organized by language so that anyone can fork the project or create a branch and add a new language.

§ Design

The design MUST be delivered in figma.

Screen captures available in the assets directory of the repo.

§ Repo, packaging and deployment

Development lifecycle must adhere to the organization rules.

When a tag is created from the main branch, it MUST deploy to github pages.

Repo for website MUST be named hologram.zone-website.

§ References

§ Normative References

RFC3986
Uniform Resource Identifier (URI): Generic Syntax. T. Berners-Lee; R. Fielding; L. Masinter; 2005-01. Status: Internet Standard.

§ TyC

TyC

§ PP

Privacy Policy

✕
Table of Contents ✕
undefined