- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Fri, 30 Apr 2021 10:14:26 -0700
- To: Jeffrey Yasskin <jyasskin@google.com>
- Cc: spec-prod <spec-prod@w3.org>
Note that there’s a “doJsonLd" configuration option, which I really don’t think should be an option or should at least default to “true". It adds a JSON-LD block to the generated spec, which includes this type of information. It is primarily intended for SEO purposes, but if it was used uniformly, it would provide a convenient means of extracting editor/author information as well as citations. The example doesn’t show the editor’s institution, but it will if provided. Note that you don’t really need to understand how to process JSON-LD in order for this information to be retrievable, but if it was done universally, it could be used to maintain an improved specRef. Gregg Kellogg gregg@greggkellogg.net > On Apr 29, 2021, at 7:51 PM, Jeffrey Yasskin <jyasskin@google.com> wrote: > > Hi editors, > > I'm looking for a systematic way to identify everyone at Google who edits a web specification. I suspect we have tools that are 90% of the way to doing that, but I'm not sure which ones are closest and would accept patches to get the rest of the way there. > > * Specref: Lists names for editors, but not their organizations. The data comes from various sources, which also don't seem to generally include organizations or email addresses, even when the source specifications do. > * Reffy: Parses specifications, which means it has access to the nice markup around editors. However, its focus is on references, not editors. > > Do y'all know of any existing list of editors? If not, which tool do you think is the right one to start from? > > Thanks, > Jeffrey
Received on Friday, 30 April 2021 17:19:58 UTC