- From: Jeffrey Yasskin <jyasskin@google.com>
- Date: Fri, 30 Apr 2021 13:01:10 -0700
- To: Gregg Kellogg <gregg@greggkellogg.net>
- Cc: spec-prod <spec-prod@w3.org>
- Message-ID: <CANh-dX=EW4xRdGBM3LwRcbNqCphYEO7+dOVW_CLg7HsLUwoyiQ@mail.gmail.com>
The format of the editor information inside the spec doesn't matter very much: a tool that's crawling and parsing HTML specs can pull out a <script type="application/ld+json"> block about as easily as it can navigate the <dd class="editor p-author h-card vcard"> that's used in non-JSON-LD specs <https://drafts.csswg.org/css-fonts-4/>. I'm more asking if there's an existing tool that is already crawling and pulling out the editor data, and if not, which tool and database I should add it to. (This would be a moment for the Semantic Web to shine, if there's some generic tool that has been opportunistically crawling what JSON-LD blocks exist in specs and pulling out their editors into a place I could just query.) Jeffrey On Fri, Apr 30, 2021 at 10:14 AM Gregg Kellogg <gregg@greggkellogg.net> wrote: > 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 20:01:35 UTC