James A. Overton

If we're going to switch to Schema 2, what do we think about having very short one-letter column names? x | current ---|--- `g` | `graph` `s` | `subject` `p`...

Yes, we should definitely do this.

Yeah, I’m open to these changes.

This must be happening in `rio`. Hopefully there's a setting we can tweak, or just update the dependency, because I do not want to get into the core of this.

@lmcmicu Can you check whether recent updates to rio_xml resolve this problem? This commit seems relevant: https://github.com/oxigraph/rio/commit/bb81f95d5cdf6dfcd278d92a2d51bf154a166fb5

I think the source of this is in `trim_text` here https://github.com/oxigraph/rio/blob/master/xml/src/parser.rs#L65 This is a setting for the underlying quick_xml: https://docs.rs/quick-xml/0.22.0/quick_xml/struct.Reader.html#method.trim_text But when I turn off `trim-text` I get errors like...

@cmungall How bad do you think it would be to bite this bullet and insist that literals cannot have leading or trailing whitespace? In ROBOT report this is currently considered...

The status quo is that the OBO registry contains data about each ontology **project**, which gets updated periodically, and the OWL files contain data about each **release**, each of which...

@matentzn Sorry, I misunderstood. I'm fine with better tooling for syncing selected values from the registry to a project.

The OBO registry is converted to RDF (see [`registry/`](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/registry/)) and mappings for all (?) of these are defined in [`registry/context.jsonld`](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/registry/context.jsonld#L30).