I don't have feedback on the recipe itself, I wholeheartedly agree with the technical recommendations. The FAIR data principles have been quite popular, and I think Signposting is a great example of practices that foster FAIRness.
That said, who's the target audience? Developers who want to ride the FAIR wave, or FAIR aficionados who want to put their metadata where their mouth is?
I think that the connection between Signposting and FAIRness is rather obvious to readers familiar with linked data, but I doubt it is as evident to less-technical readers (who might still be familiar with FAIR, because it's everywhere these days).
The body of the document is fairly technical—I always assume that half of the audience will browse away at the first sight of monospaced fonts—and I'm not sure less-technical readers will understand that:
- Increasing the FAIRness of scholarly objects for machine agents also increases their FAIRness for humans
- Signposting has a ridiculously low cost of entry (if you serve scholarly content over HTTP, you're already almost there)
Specifically:
- "a concrete recipe that repositories can follow": will publishers understand that their websites are included, too, when you mention repositories?
- "widely implemented web protocols specified in IETF RFCs": while this is true, it doesn't really highlight the low cost of entry of Signposting (we're talking about HTTP headers, which any web dev should be able to tweak)
(I might be projecting my own insecurities about persuading non-technical audiences.)
I don't have feedback on the recipe itself, I wholeheartedly agree with the technical recommendations. The FAIR data principles have been quite popular, and I think Signposting is a great example of practices that foster FAIRness.
That said, who's the target audience? Developers who want to ride the FAIR wave, or FAIR aficionados who want to put their metadata where their mouth is?
I think that the connection between Signposting and FAIRness is rather obvious to readers familiar with linked data, but I doubt it is as evident to less-technical readers (who might still be familiar with FAIR, because it's everywhere these days).
The body of the document is fairly technical—I always assume that half of the audience will browse away at the first sight of monospaced fonts—and I'm not sure less-technical readers will understand that:
Specifically:
(I might be projecting my own insecurities about persuading non-technical audiences.)