Design and implement some form of flexible header, manifest, or metadata information for split QR streams.

[xloem]

See some comments on #19

[mofosyne]

aye. Ideally it should not be a binary container, but in plaintext.

If possible, but not mandatory, it would be nice if it can be detected and launched from zxing barcode reader app directly under "open browser" button after a successful scan of the manifest barcode.

[xloem]

That sounds great. Good reason to use a datauri. Briefly reviewing the zxing source I think a wide variety of loosely uri-like prefixes would fit that.

[mofosyne]

anything you had in mind? You don't need to choose from what zxing explicitly allow for, after all, datauri is not supported by zxing directly.

The way I think zxing works out if it is a url or not, is if it fits this format <schema>:<charactersExceptSpaces>

If it is, it would just send it directly to android OS as a uri intent, and let android sort the resolution of the schema (e.g. web browser would listen to "http:", while tagdrop listens for "data:").

So we could choose any keywords we want, but ideally it shouldn't be an existing internet standard, unless we are going to keep in lockstep with it's syntax to avoid breaking other parsers.

[mofosyne]

btw how shall we keep in sync the extended datauri implementation? Perhaps we keep in touch over email? My email is mofosyne @ gmail . com

Oh and for your information, I had a though on extending datauri to span multiple qr tags in a transparent manner mofosyne/tagdrop#11