Ben: getting feedback from usmca cred. This changes order, reflect what doc loooks like originally. This does it for us exporter, importer, and made minor changes to flags ✪
Orie Steele: [...] Json schema preserves order. They don't have prop that json-ld has. yaml will maintain order, and if json-ld need order can annotate that order is important ✪
Nis Jespersen : That's it on PRs, on to vocab issues ✪
Orie Steele: Still needs to be done. every time @type & points to not great, destroy value of json vocab. If don't do good job here, get bad graph data, undermines point of rdf in first place ✪
Nis Jespersen : Ben, assigned? oh, dropped, keep him assigned then ✪
Nis Jespersen : 462, Ben, assigned to mahmoud. ben? ✪
Ben want to close this. back when we were doing more common & grouping things, what class does this refer to. We've been switching toward direct doc & using context ✪
Nis Jespersen : Inlining we've been doing, seems moot point ✪
Nis Jespersen : I'll comment but ben your ticket, you suggest we don't need this anymore? ✪
Ted Thibodeau: If only ever have one or other in realworld, would do that, could in comment mention the alternate attribute and/or have two examples (i.e., one with each attribute) ✪
Ben: pointing out we have two possibilities of examples. One is in bottom combined cred, other is in yaml part. can have ex for each in yaml, with one realistic in json bottom of file. ✪
Nis Jespersen : If we were to start using, need to agree on how. One fill everything out, other to look realistic? ✪
Ben: in schema, here's descr locode, here's ex value, here's port code, here ex value. independent of each other I think. ✪