Global Feed Post Login
Replying to Avatar hodlbod

If divergence in UX justifies divergence in data formats, then every distinct UX would have its own data format, and there would be no interoperability.

On the other hand if semantics justify data formats (e.g. we've arbitrarily decided that short form video vs long form video are different concepts on an ontological level), then divergent UX can interoperate.

The difficult thing is deciding what the trade-off should be between simplicity (by collapsing multiple types of thing into a single standard) and complexity (proliferating standards and granular tags for more complete support of more use cases).

The limiting factor is simplicity. Once a spec becomes too complex, the number of implementations drops significantly. Therefore, in order to support interoperability, applications have to interoperate on a level below their desired UX, and supplement either through inferring additional meaning from the base data formats (which logic may diverge between clients) or by creating proprietary data formats to support the client's UX.

Avatar
Alex Gleason 10mo ago

The answer: a mix of both

Reply to this note

Please Login to reply.

Discussion

Avatar
hodlbod 10mo ago

Yeah, obviously we can't go to ultimate simplicity or else there would be no information in the specs.

Thread collapsed