Val Lorentz

because `"foo bar"` is not a URI, so it's not a valid `@id`. Which means the `"identifier": { "@id": "schema:identifier", "@type": "@id"},` rule in the context can't be used to...

only for values that satisfy the type constraint

Why are you talking about a validator? This changes the behavior of any spec-compliant implementation of the JSON-LD compaction algorithm.

Actually, it changes the behavior of the expansion algorithm too: ```json { "@context": { "schema": "http://schema.org", "identifier": {"@id": "schema:identifier", "@type": "@id"} }, "identifier": "https://example.org" } ``` is expanded to: ```json...

IRC has different concepts that may be called "username": the ident, the gecos/realname, and the SASL username. Soju's documentation you linked doesn't clarify which one it calls username. However, `@`...

Please update the description in `_irc/index.md`

You don't need to fetch the list of providers; the title snarfer already downloads the start of the page so it can look for `` tags

Alright, it should support both then. Open a PR with support for both registry and discovery, configurability, and a couple of tests and we'll work on that. Also, the registry...

Codemeta does not support this, and I don't see anything close in schema.org. This seems out of scope for Codemeta (IMO), but could be suggested to schema.org. And since Codemeta...

we could make it configurable while keeping `[^\w\s]` as the default