...
Requirements and Desiderata
- At minimum, ?info must resolve to a human readable landing page, and should provide a gateway to machine-readable metadata
- It is strongly recommended that meta tags with [something like] DC are implemented (I’m suggesting this since they are simple html, and all orgs should be able to do something with those)
- Secondary to this, we encourage organizations to use whatever data format[s] is appropriate in their context as the machine-readable data version of ?info, but encourage that:
- Organizations include DC and/or schema.org metadata where possible
- Organizations use XML or JSON-LD serializations to express their
- Organizations utilize either content negotiation or queries in the form “&format=[json|xml|etc]” property to deal with alternative formats.
- Some continuity with past
- human- and machine-readable metadata returned
- including persistence statements
- who/what/when/where paradigm (ERC)
- THUMP-like request protocol -- ?info(X,Y) vs ?info&arg1=X&arg2=Y
- Never RDF
- unfortunately, JSON-LD is RDF; see tweet https://twitter.com/justin_littman/status/1206944465027584001
- however, widely used schema.org borrows elements names from JSON-LD and uses them in meta tags, which aren't at risk of RDF complexity
...