2020-01-06 Technical WG Agenda and Notes

see new section at top of Inflection change proposal

Karen/Bertrand

1. At minimum, ?info must resolve to a human readable landing page, and should provide a gateway to machine-readable metadata
2. 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)
3. 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:
   1. Organizations include DC and/or schema.org metadata where possible
   2. Organizations use XML or JSON-LD or JSON serializations to express their
   3. Organizations utilize either content negotiation or queries in the form “&format=[json|xml|etc]” property to deal with alternative formats.

John

1. Some continuity with past
   1. human-readable metadata returned
   2. machine-readable metadata returned
   3. including persistence statements
   4. who/what/when/where paradigm (ERC)
   5. THUMP-like request protocol -- ?info(X,Y) vs ?info&arg1=X&arg2=Y
2. Never RDF
   1. unfortunately, JSON-LD is RDF; see tweet https://twitter.com/justin_littman/status/1206944465027584001
   2. 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