Erik Wilde

On 2016-02-17 08:03, Asbjørn Ulsberg wrote: > Could Microformats http://microformats.org/wiki/microformats2 be > considered a registry? HTML5's list of link types > https://www.w3.org/TR/html5/links.html#linkTypes and namespaces > https://www.w3.org/TR/html5/infrastructure.html#namespaces are most > definitely...

adding XForms, more coming soon... https://github.com/dret/hyperpedia/commit/afd5201dfe6116b677ccd0a20c273cf4446864b1

> On Jun 24, 2018, at 09:24, Mike Amundsen wrote: > LinkRel pattern seems like the right one to me. > registry to hold agreed labels > extension pattern for...

here's a starting point, feedback and comments greatly appreciated: the format model should have _a title_ for each format, and a _unique identifier_. if a format has various version/variants, then...

there is a possible alternative approach, which is using dedicated profile negotiation header fields: https://github.com/ProfileNegotiation/I-D-Accept--Schema (by @larsgsvensson and @RubenVerborgh)

still waiting for feedback from @jasnell, but for now assuming that a `profile` preference would be in line with the intention of the `Prefer` header field.

On 2018-03-17 13:05, James M Snell wrote: > Sorry @dret ! Just spotted this again! Yeah, I > think that's fine that's good to hear, and thanks for your response!

@larsgsvensson: that would be the same as what happens if the server simply does not understand or ignore the `Prefer` header: the server does whatever it want to do. preferences...

On 2018-03-23 11:44, Lars G. Svensson wrote: > OK, thanks. But then there is no way the client would know which profile > the data conforms to, as opposed to...

not sure i fully agree, but that's certainly a matter of perspective and interpretation. for our main use cases, i'd like to be linked to a non-deprecated "version" of the...