<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[There is also the other question of — would the resume &#x2F; CV be JSON-LD.]]></title><description><![CDATA[<p class="quote-inline">RE: <a href="https://mastodon.social/@reiver/116597841178183282" rel="nofollow noopener"><span>https://</span><span>mastodon.social/@reiver/116597</span><span>841178183282</span></a></p><p>There is also the other question of — would the resume / CV be JSON-LD.</p><p>On one hand, if it was in JSON-LD, it would make it machine-legible similar to ActivityPub.</p><p>On the other hand, I don't think anyone is going to write JSON-LD (especially HTML embedded in a JSON string value) by hand. But, I do think some people will want to write their resume by hand.</p><p>It feels like user-experience is fighting with JSON-LD based machine-legibility.</p><p><a href="https://mastodon.social/tags/ActivityPub" rel="tag">#<span>ActivityPub</span></a> <a href="https://mastodon.social/tags/ActivityStreams" rel="tag">#<span>ActivityStreams</span></a> <a href="https://mastodon.social/tags/FediDev" rel="tag">#<span>FediDev</span></a> <a href="https://mastodon.social/tags/ProToGo" rel="tag">#<span>ProToGo</span></a> <a href="https://mastodon.social/tags/JSONLD" rel="tag">#<span>JSONLD</span></a></p>]]></description><link>https://bb.devnull.land/topic/6ba65f04-d1ff-4a97-bc37-5dcb7cf4f584/there-is-also-the-other-question-of-would-the-resume-cv-be-json-ld.</link><generator>RSS for Node</generator><lastBuildDate>Sun, 07 Jun 2026 10:48:44 GMT</lastBuildDate><atom:link href="https://bb.devnull.land/topic/6ba65f04-d1ff-4a97-bc37-5dcb7cf4f584.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 18 May 2026 22:14:05 GMT</pubDate><ttl>60</ttl></channel></rss>