Volker Mische

> This seems redundant, and I question the utility of it. I guess the idea is that we like self-described data over spec'ed data? Without the prefix it's Base64 encoded...

> For a codec there really should be _just one way_, Agreed. And as we especially would like to enforce that, I think it makes sense changing it from Multibase...

There are more details about string in the data model document in the [String kind section](https://github.com/ipld/specs/blob/15751f5be4aa31dbf8c1446e5f1f2a621be4dff7/data-model-layer/data-model.md#string-kind). There has been a long discussion about it and the conclusion was that string...

> UTF-8 is a specific binary encoding though, which seems out of scope for a conceptual serialization-agnostic data model. Agreed. Sadly there isn't a sharp boundary between the conceptual level...

> I'll go with using a `Text` unicode string type that will always spit out valid `utf-8`, but will not successfully round trip invalid utf-8. @tysonzero This is what I...

@mikeal Wouldn't it make sense to first spec this out in https://github.com/ipld/specs/blob/2a5c3575f28b9393998ec121b6c8b239df4df9f2/block-layer/codecs/DAG-CBOR.md first? People reading the dag-cbor spec should be able to implement it easily in a compatible way,

@rvagg I would describe how numbers need to be encoded, e.g. that floats without decimals (or only zeros as decimals) are encoded as integers (or not, depending on what we...

@mikeal it's more a "getting-a-lot-done" rather then closing. Most open things are valid things that need some work (in the previous round we were able to close old/out of scope...

~The SoftWare Heritage has a case where things are encoded as Git objects, but in order to process it you need more to know which time it is as the...

As I'm a fan of tooling and automating things, I'll take this issue and when working on it, I can just try both and see which one does a better...