@reiver ⊼ (Charles) :batman:@reiver@mastodon.social: I may have written a JSON-LD schema for JSON Resum…

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @reiver@mastodon.social
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-20 02:45:23)
My personal desire would be to create a format from scratch (because you are in control, you get something bespoke to your needs, and it is personally satisfying), but —

I think there is probably an advantage to using something (such as JSON resume) that already has wide adoption.

I guess that makes me inclined towards the latter.

...

So, if I go that way, I would have to decide: plain JSON or JSON-LD.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume
---Reply---
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-20 23:13:47)
I may have written a JSON-LD schema for JSON Resume.

It is defined in terms of ActivityPub.
For example:

'Resume' is a sub-type of an ActivityPub 'Object'. There are some new fields defined. Etc.

...

Now the question is — where do I put it?

Do I create a pull-request to the JSON Resume resume-schema repo?

Do I create a FEP?

Do I put it somewhere else?

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONresume


---Replies---

@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-21 04:55:59)
Here is my work-in-progress FEP for using JSON Resume with ActivityPub:

FEP-6158: ActivityPub 'Resume' Object: JSON Resume expressed as JSON-LD

https://codeberg.org/reiver/fep/src/branch/fep-6158/fep/6158/fep-6158.md

I prefer to write for clarity, so it still needs work.

#ActivityPub #ActivityStreams #FediDev #ProToGo #JSONLD #JSONResume #fep6158 #fep_6158