Identifying W3C crawlable pages

[egekorkan]

Given that W3C is now creating pages for all WG, IG, CG automatically with the following information:

• Summary
• Participants
• Publications
• Links to charters
• Calendar

We have to ask ourselves whether we should maintain them manually again at:

• https://www.w3.org/WoT/wg/
• https://www.w3.org/WoT/ig/
• https://www.w3.org/WoT/activities/meetings/
• Contact (partly our own links)

The part that W3C does not cover is the Task Forces and what Community Groups are linked to WoT.

The following pages are more or less community-oriented information:

• Events (https://www.w3.org/WoT/activities/events/)
• Developers
• Documentation
• Videos
• Contact (partly our own links)

We need to maintain these ourselves since we are curating them

[egekorkan]

Worth to note is that the JSON-LD webpage (https://json-ld.org/), which is not under W3C, has no information about the WG, it is about the technology first and it links to the specs.

[egekorkan]

Call of 20.12:

• We had a look at the W3C API at https://api.w3.org/doc and tried it out with API Keys generated by @egekorkan . The data seems to be available for us to simply reuse (except for Task Forces).
• Our initial approach will be to use the https://github.com/w3c/apiary to generate the data on the client side on demand. The API Key needs to be limited to the domains of w3.org/wot and netlify and github.io . It has a limit of 5000 hits per 1 hour. We have about 2000 visits per month, which should be fine.
• @egekorkan will do some tests for next call after holidays.

[egekorkan]

I have just noticed that the limit of the API Key is 5000 hits per hour. I was not sure what a hit means but I have found https://w3c.github.io/w3c-api/ which says that hit means request and also that systems team can increase the limit.

By default, each key can make up to 5000 requests per hour. W3C Systems team can increase that limit.

Also it says:

If API keys are going to be publicly visible (for example in some client-side Javascript code), it is highly recommended to specify allowed domains when creating or editing them.

This means that they are ok that we put it in the client side but restrict to the domains in the comment above.