diff --git a/0004-general-uri-scheme/general-uri-scheme.adoc b/0004-general-uri-scheme/general-uri-scheme.adoc index d4773b5..7d1a763 100644 --- a/0004-general-uri-scheme/general-uri-scheme.adoc +++ b/0004-general-uri-scheme/general-uri-scheme.adoc @@ -336,9 +336,9 @@ include::data/test/tc05[] ==== The Resource Type and Identity -While <> allows you to refer to a Git repository, +While <> allows you to refer to a Git repository, it may also be desirable to refer to one or more specific resources within -that repository. To do this, <> may be followed +that repository. To do this, <> may be followed by a "/", a resource type and identity. By default, the resource type and identity is nothing, left to be added @@ -435,8 +435,8 @@ parameters `tree`, `blob` and `path` to refine the `rad:` URI. -- The identifier that follows this type must be a Git object identifier. -With this resource type, it makes no sense to use any of the <> defined above. +With this resource type, it makes no sense to use any of the +<> defined above. -- `tag`:: @@ -725,7 +725,7 @@ include::data/test/tc32[] * Implementations may implement only part of this specification, depending on what makes sense in the context of what they do. It is advisable, however, if -they can parse enough of a valid `rad:` URI to allow for <>. +they can parse enough of a valid `rad:` URI to allow for <>. For example, it is hard to imagine that `git-remote-rad` would ever support more elaborate URLs than those involving an RID and an NID: @@ -762,9 +762,9 @@ other patches in the same repository with `patch/{PATCH-ID}` or `issue/{ISSUE-ID Future work may include: -* amending <> with Radicle network +* amending <> with Radicle network specification syntax (pending future formalization of that idea). -* amending <> with multi-device IDs (also +* amending <> with multi-device IDs (also pending formalization of that idea). * adding more resource types, and their respective syntaxes * extending existing resource types.