content-disposition vs data URI

[Case Duckworth]

In the Vcard example, I don't see why you couldn't put the Vcard between code fences. Optionally with an alt text starting it's a Vcard, if the client wants to get fancy. Otherwise, you could just copy and paste it.. it's a text format, after all. 

Which makes me think: there's two kinds of things these 'data:' URIs (which I am against, tho not on a protocol level; I just don't think any client will bother with them): text and binary-encoded-as-text. For the text, just fence it if you really want it inline. For binary, just link them. Surely encoding a binary file as text takes up more space than it does in disk! If a client really wants to display it inline, they can do another request and go totally off spec. If they just have to. 

On Thu, Jun 4, 2020, at 10:48 AM, Jason McBrayer wrote:
> Petite Abeille <petite.abeille at gmail.com> writes:
> 
> > Additionally, perhaps text/gemini could embraces data url as small inline adornment.
> >
> > For example, given a small data encoded vCard, 917 bytes long:
> >
> > data:text/vcard;charset=utf-8;base64,QkVHSU46VkNBUkQNClZFUlNJT046NC4wDQpOOkd1bXA7Rm9ycmVzdDs7TXIuOw0KRk46Rm9ycmVzdCBHdW1wDQpPUkc6QnViYmEgR3VtcCBTaHJpbXAgQ28uDQpUSVRMRTpTaHJpbXAgTWFuDQpQSE9UTztNRURJQVRZUEU9aW1hZ2UvZ2lmOmh0dHA6Ly93d3cuZXhhbXBsZS5jb20vZGlyX3Bob3Rvcy9teV9waG90by5naWYNClRFTDtUWVBFPXdvcmssdm9pY2U7VkFMVUU9dXJpOnRlbDorMS0xMTEtNTU1LTEyMTINClRFTDtUWVBFPWhvbWUsdm9pY2U7VkFMVUU9dXJpOnRlbDorMS00MDQtNTU1LTEyMTINCkFEUjtUWVBFPVdPUks7UFJFRj0xO0xBQkVMPSIxMDAgV2F0ZXJzIEVkZ2VuQmF5dG93biwgTEEgMzAzMTRuVW5pdGVkIFN0YXRlcyBvZiBBbWVyaWNhIjo7OzEwMCBXYXRlcnMgRWRnZTtCYXl0b3duO0xBOzMwMzE0O1VuaXRlZCBTdGF0ZXMgb2YgQW1lcmljYQ0KQURSO1RZUEU9SE9NRTtMQUJFTD0iNDIgUGxhbnRhdGlvbiBTdC5uQmF5dG93biwgTEEgMzAzMTRuVW5pdGVkIFN0YXRlcyBvZiBBbWVyaWNhIjo7OzQyIFBsYW50YXRpb24gU3QuO0JheXRvd247TEE7MzAzMTQ7VW5pdGVkIFN0YXRlcyBvZiBBbWVyaWNhDQpFTUFJTDpmb3JyZXN0Z3VtcEBleGFtcGxlLmNvbQ0KUkVWOjIwMDgwNDI0VDE5NTI0M1oNCngtcXE6MjE1ODg4OTENCkVORDpWQ0FSRA==
> >
> >
> > A client MAY render it inline, for the user to interact with, in any appropriate ways:
> 
> Please, no. I'd be all for a client rendering text/vcard and similar
> content types as pages, with whatever formatting the client author
> likes, but they should be rendered as separate documents. If you want an
> inline link preview, you can write it by hand, or have it generated by a
> script. 
> 
> -- 
> +-----------------------------------------------------------+  
> | Jason F. McBrayer                    jmcbray at carcosa.net  |  
> | If someone conquers a thousand times a thousand others in |  
> | battle, and someone else conquers himself, the latter one |  
> | is the greatest of all conquerors.  --- The Dhammapada    |  
>