While improving text around the self link, noticed that the ids
were wrong on one of the example...

It seems likely to be related to embedded collection item
representations and whether they can b...

For some reason the reference to the Atom RFC, where "self" was
originally defined, was commente...

Normalize "client" terminology

...based on review feedback.

This should be enough to give a feel for the basics without
needing a detailed explanation or ta...

Avoid "client" on its own where possible. Use "client application",
"user agent", and "client i...

Numerous improvements to security considerations

While "targetSchema" is technically never required to process
a response, as the response should...

The other parts flow much more naturally from the mention of
RFC 8288 in the introductory part o...

8288 is the update of 5988 Web Linking. As a link serialization
format, Hyper-Schema shares tho...

This was an awkward copy-paste. Fix it up and remove the CREF
reminding me to do so.

Since I have no idea what it is trying to do.

Typo fixes

Rebase previously approved PR

Only Hyper-Schema included a space, so get rid of it.

RFC 7322 references Chicago Manual of Style rules, so title
case include capitalizing minor word...

Feedback from awwright.

Rework collection example for clarity

More review feedback on the collection example.

replace href* keywords by template* in collections example

* Restate the item resource, including the newly added "collection"
link.
* Remove some of the...

Give HTTP POST discussion its own section.

This was left in the HTTP and targetSchema section, I think by
accident. Let's give it its own ...

Move up the JSON Hyper Schema in "mailto:" example

Rework '"targetSchema" and HTTP'

Improve the hyper-schema abstract

Use language more in line with recent changes and recently
introduced concepts. Add a little mo...

Better wording in HTTP "targetHints" section

While reading this section, I felt that the example came too late after
a lot of explanations on...

Split collections example (and rename items to elements)

Do a basic collection/item example, and then add pagination as
yet another example.

In the collection example, it's (probably) more confusing to
have the actual collection array na...

This is an attempt to introduce concepts in a better order
and generally improve the flow. Exam...

Fix trivial typos, remove leftover cref

Improve wording with feedback from awwright

A couple of edits/fixes in hyperschema spec

Those assertion/applicability/attachment definitions got moved.

Because it's much better than what I had there :-)

which probably should have been an XML comment anyway

Example using "anchor", "base", "templatePointers"

The long lines basically worked but caused warnings.

It also shows why "rev" is not necessary (it is deprecated in
other link specifications, so it i...

Replace RFC 5988[bis] with RFC 8288

The update to RFC 5988 has been published as RFC 8288.

Guidance on content negotiation

Mostly just refer to the core spec and note that there are many
approaches depending on the use ...

...and a few other minor wording improvements around HTTP usage.

Changelog for hyper-schema

Add request/response implementation requirements

This mostly involves explaining that hyper-schema is not a system
for executing requests and pro...

Add most of a collection example.

There are some things that are not addressed here, and most
importantly this highlights the prob...

Rough draft of a few examples

We need a list of templates as the href template and any
relevant base templates need to be reso...

This is just to get the conversation started about this approach
to examples.

This one for different sorts of input, as well as different
uri schemes and media types.

Rewrite the Hyper-Schema spec almost entirely

Target attributes are advisory, and MUST NOT be considered
authoritative.

While it is technically not a primary part of the specification,
but rather an application of th...

Also improve the wording introducing the output format.

Split the "links" fields off from their...

Now that the implementation requirements have been moved down
below the keywords, they can be su...

A lot of this should go on some sort of best practices guide
on the web site. This cuts quite a...

Per discussions with other project members given the rewrite
effort.

Now that we have "targetHints" which, among other things, can
provide information about which HT...

Minor tidying and removal of an unnecessary reference.

Define the condition for using hrefSchema more clearly (I hope).

Use consistent language around...

and note that it is a serialization of the abstract link
model from RFC 5988bis

When discovering links for a hyper-schema, it does not make
sense to examine the schema keywords...

It does not need as much detail, and I had left out the important
application towards server push.

Re-organize the first few sections a bit (based on looking at
how several other relatively recen...

Here are the main changes:

* Set context in the overview and explain purpose. This should
pr...

New overview based on applicability and assertions

This updates a section number in hyper-schema for the moved
definitions in validation, and rewor...

URI Template resolution as pseudocode