What is a common approach when building API Server from swagger spec file (usually swagger.yml).
Command swagger generate server... generates a bunch of .go files. Where those generated .go files should be placed.
Is a good approach to put them to /pkg/api/ ?

See https://url.spec.whatwg.org/#goals and https://url.spec.whatwg.org/#url-apis-elsewhere.

This is especially important in the public API (the "uri_handlers" key should be "url_handlers"), but changing the proposal name and all the prose is also important.

Per mikewest:

No, cross-site frames should not be able to access SameSite=AnythingButNone cookies via document.cookie. The spec doesn't make this clear (you have to read between the lines of bullet 5 of step 1 of https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-06#section-5.5), so we should change the spec.

ATM "Scans file" can contain prescribed acq_time column (which could be anonymized or not) and an arbitrary number of additional columns: "Additional fields can include external behavioral measures relevant to the scan.". I think the situation is similar to _events.tsv file which now is SHOULD ha

Both caching and semantics make some references to h1-messaging. They should not be normative.

We can do this by:

• Removing unnecessary references
• Turning references into examples / advisory text
• Clarifying H1 specificity where appropriate

Includes #332, #333, #311, #259, #183, #182, #118.

See today's thread on gen-art about this.

The answer to:

Why aren't per-directory well-known locations defined?

Given in Appendix A could be moved into Section 3.

  Allowing every URI path segment to have a well-known location
  (e.g., "/images/.well-known/") would increase the risks of

What seems to be the problem (1 sentence)

Folks should be entering their Linkedin username only on author pages. Not the whole URL. Need to scan the site and check for author pages that include "http" in the Linkedin value.

example: https://digital.gov/authors/bridget-fields/

We needed this yesterday on models.Molecule. Posting it in case anyone wants a starter project. Should test on example that does and doesn't have fix_com set. (True should give origin.)

In the plugin manager, the lateral panel showing the plugin information should also contains some documentation in order to explain how the plugin works.

A standard test suite for QC programs should be curated that run over several dimensions at a minimum:

• Driver: energy/gradient/Hessian
• Reference: UHF/RHF
• Relevant procedures: optimization

MDN does a good job describing some of these standards, e.g. https://developer.mozilla.org/en-US/docs/Web/HTTP. It would be a useful addition to the other human readable docs.

Phil Note: Link to any tutorials, guides, and MDN. Should support anything.