Roberto Polli
Roberto Polli
@awwright I think the distinctions you made are relevant. Especially, it is key to define whether: * something is beyond the scope of the document (e.g. is left to the...
> most of our rationale for undefined behavior should be self-evident imho "Explicit is better than implicit" :P > what do you mean by "NOT RECOMMEND or FORBID"? You are...
I don't have preferences between abnf and regexp. Here and elsewhere in this document, both are ok as long as it's not in prose :) > we would want to...
> ... e [WC3 Best Practices for Fragment Identifiers and Media Type Definitions](https://www.w3.org/TR/fragid-best-practices/#structures) (which is also cited elsewhere in JSON Schema Core) references the XML NCName Ok, it wasn't clear...
When I first read the spec, I found that defining json schema as a media type was confusing, since iiuc a media type is a "label" for some content. Stating...
Hi @awwright, let me clarify + forgive the nitpicking > The JSON Schema spec is being submitted as an Internet specification, or at least must be compatible with Internet standards....
Thanks!
Even just warning that the default is generating v1 model is ok.
It seems to work now with rdflib 7.0.0 (tested via ttlser) ```bash $ echo ' @prefix foo: . foo:a "ciao" . ' | ttlfmt @prefix foo: . ### Annotations foo:bar\(ciao\)...
> Regardless, this is something we can discuss if the draft is adopted. Agree. The semantic now is core. > the current draft is compatible with some implementations out there...