Gregg Kellogg

> @gkellogg wrote > > > YAML tags already use an expression for URIs, although possibly not completely compatible, and with implementation issues for things like '#'. > > Can...

> @anatoly-scherbakov I also worry about non-standard YAML parsers (even before this issue), since I haven't seen any parser to properly handle custom tag definitions. As @gkellogg wrote, you can't...

This issue was discussed in the 2022-10-12 meeting. Subtopic: Extended Internal Representation yaml-ld#84 ✪ https://github.com/json-ld/yaml-ld/issues/84 -> Issue 84 Downgrading from Extended Internal Representation should use value objects (gkellogg) enhancement, spec...

In the call, I discussed my S-Expression representation of, for example, SPARQL. This is essentially the AST that comes from parsing the SPARQL grammar into a form that can be...

This was discussed during today's call: https://json-ld.org/minutes/2022-06-22/.

This issue was discussed in [today's meeting](https://json-ld.org/minutes/2022-07-20/).

I think this is a great candidate for something an _extended profile_ could do, and something like the `%TAG ! http://www.w3.org/2001/XMLSchema#` seems like a great way to go. In my...

I guess in my mind, the "YAML-JDON-compatible" profile is analogous to YAML using the [JSON schema](https://yaml.org/spec/1.2.2/#json-schema). This does not depend on explicit tags, but implicitly associates the values with `tag:yaml.org,2002:null`,...

I've looked into this some more as part of trying to implement extended support for XSD scalar values in YAML. IMO, the appropriate `%TAG` value would be something like the...

> * is it at all feasible to write `"foo"@en` in YAML rather than a separate `@language` field? No, I don't believe it is, however, we could consider using a...