Language and direction tags in CBOR literals

[chrysn]

Given that our compact URIs became more widely usable in CBOR, might we do the same things for languages?

Like, define a tag structure #6.TBD([tstr, lang, ?direction]) that enables I18N for general CBOR.

With our data model it'd work just the same, we could ditch the attributes-on-literals unless another use case shows up. (Note: I like attributes on literals. But they have to carry their weight in the information model).

Actually we already have one (tag 38) shaped #6.38([lang, tstr]); it should be extensible still to allow a direction (given that the author mentioned RDF as a use case where that was added).

[edit: link to spec, fixed example]

[chrysn]

Pulling in that tag could happen within notable-tags.

Next step: Contact Peter, make suggestion, see if he responds. true/false as suggestions.

[chrysn]

This has moved into problem-details, and just needs some text now that ties it together with the RDF conversion.