Re:Getting to Xanadu
by jonathankoren on Saturday December 08, 2018 @05:49PM
(#18638001)
Why would you embed an image file, instead of just link to it? That’s not the problem at all.
The problem is just simply knowing that “1935” is a number, and a date. Microformats somewhat address this, but it has limited uptake.
But relying on people to tag stuff correctly, isn’t going to work. Just look at the mess that META tags are, especially those outside of share card population. I’m not talking about reading the spec. I’m talking about seeing how they’re actually used. People can’t even get “tags” right, let alone “author” or “date”
Very true. We feel like this is an area where better tools can help. I hesitate to use the term "AI" because I don't think artificial intelligence is real. But I do believe that tools can be designed to act more intelligently, including identifying the source and context of our writing without us explicitly having to take a hand in it.
Not just an image file. A spreadsheet. A database extract. A genealogical record.
The tagging problem is constant across all formats.
<DATA type=application/foobar encoding=base64> .... </>
which could include application/json, application/epub+zip, application/pdf, whatever. If the browser knew how to handle it natively, great; if it knows how to invoke a helper for that, good; if nothing else a link appears to save it as an individual file.
If you give a DATA entity a name tag, you can use it inside the same page anywhere a suitable use occurs:
<DATA name=parrot.jpg type=image/jpeg encoding=base64> ... </DATA>
<IMG SRC=#parrot.jpg>
Best if you make all the attributes of the original tag follow along, so:
<DATA name=#parrot.jpg alt="Parrot Rights Now!">...</>