~ivilata/gwit-spec

f4a5baff73d2a1c8902694fb1715e20e335a2abf — Ivan Vilata-i-Balaguer 16 days ago f06be2f master
Mention URIs in the introduction to basic concepts.
1 files changed, 2 insertions(+), 0 deletions(-)

M README.md
M README.md => README.md +2 -0
@@ 62,6 62,8 @@ To get content from a site, one needs to access an existing copy of it. That cop

Since gwit is based on Git, a gwit site is made up of *static files and directories*. Except for a few files with site metadata (described below), the specification does not mandate any structure or file types.

gwit defines a URI format (described further below) that allows to refer (link) to a file or directory by its path in a site indicated by its identifier. The URI may apply to an optional specific version of the site.

**Note:** As an example of how to bind the author's day-to-day key to a particular site, the latter may include some statement, signed by the author's day-to-day key, claiming ownership of the site key by its fingerprint. Or following the [Ariadne Identity Specification][AIS], the day-to-day key may include an identity claim with a gwit URI pointing to a file in the site that contains an identity proof for the key.

[AIS]: https://ariadne.id/