> If there is no way to find out whether a given COinS is valid, I
> strongly doubt that COinS is the right direction at all.
This is an excellent point, and one I was just discussing with
somebody else yesterday. The key thing to remember is that COinS is
really just OpenURL - it's only a convention for rendering an OpenURL
in HTML. Which means that we inherit all the benefits and drawbacks
that entails, one of which is that there's no clear validation
strategy for OpenURLs.
In my experience, it's surprisingly easy to dig into Zotero's
to the fields you're providing. But it's also difficult if, as you
are, you're trying to provide a COinS for something that isn't a book
or journal article - the two most common OpenURL cases, for which
Zotero's logic is optimized to some degree (and reasonably so). It
might just mean having to shoehorn an extra value into an OpenURL
profile implementation that you wouldn't otherwise use in a way that
doesn't quite make sense, but nonetheless works.
More directly to your point, though, maybe there is an opportunity for
a handful of COinS producers/consumers to write a simple set of
implementation guidelines to say "here's the bare minimum for these n