Irakli Gozalishvili

I also would like to call out that I find this structure to be really confusing ``` { $TYPE: $IDENTIFIER, "cap": $CAPABILITY } ``` I think simply making it following...

> @expede I do share the dissatisfaction with packing two fields into a single key and it may indeed be a bad idea. Maybe it is indeed better to let...

> This is surprising! If they have a fallback to raw strings, then ones referenced from that format should still maintain that ordering, no? UCANs generated initially from the CBORJSON...

> @Gozala Random idea that I'll move to the spec: would it be helpful to have an optional flag in the header that says "this is in a lexicographical sorted...

> Glad I just found this! I'm going to try it out! @Gozala I know this isn't the best place to bring it up, but how can an extension export/import...

I was about to report this (as I keep running into it a lot) and turns out there is already an issue. I was wondering if capturing styling by serializing...

Alternative strategy might be to inline all the styles into elements themselves by obtaining those through [`getComputedStyle`](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle) API. But that is likely to increase overall page size.

> You mean we would, for example, create two `` elements, instead of keeping one link to a sheet that imports another? This could be an optimisation to flatten the...

Thanks for your interest @markwylde and I totally agree that type checking is better done at compile time as at runtime it's far less useful. That being said I don't...

Unfortunately I am no longer able to maintain this project, I apologize. If someone wishes to step up and take leadership of this project please respond to #21