Gregg Kellogg
Gregg Kellogg
@no-reply I'm assigning this to you to apply your patch.
Thanks @dontcallmedom. I perhaps should have just created the issue, but I thought there may have been some requirement I was unaware of. The error comes up in the "Generate...
Thanks @sidvishnoi. It would be great if it were easier to find the specific causes of errors in the GH Action output; I had missed the link-checker error, but it...
Before I started using w3c/spec-prod, I worked with lycheeverse/lychee-action for doing link checks. It wasn't perfect, either, but did have some options and patterns to limit the links it would...
Is there a workaround, perhaps to just skip the link checker? It's interfering with various update processes.
IIRC, the WG determined that it was outside scope to actually define how to specify a frame to use when requesting framed document form. This is discussed in the transcript...
You can request 1.0 via the API, but there's no CN way to do it that I can think of. The rationale was that 1.1 was forwards compatible with 1.0,...
The original person asking to be able to specify a frame as part of a request was @lisp, who may have done something based on the WG discussions.
Summary: Clarify that "lexicographical order" means "code point order" and change some wording to reflect. See #153.
There's some odd special-case stuff going on here. Because "ex:info" is defined with `@type`: `@json`, the content of the frame gets expanded as a value object. Normally, the value either...