RE: https://mastodon.social/@reiver/116597879302607072

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

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

RE: https://mastodon.social/@reiver/116597879302607072

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

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

@reiver I've seen this thread from you, and sorry for being negative but I just have to ask: what's wrong with having a link to your CV in a PDF format in the content of your Actor's profile? We don't need to make everything an ActivityPub object in my opinion.

@mariusor

It is a fair question.

...

My thinking is —

If the resume is in JSON, JSON-LD, or some other machine-legible format, then —

Applications can render the resume / CV however they want (and aren't just displaying the way it was rendered in the PDF).

Tools can edit JSON, JSON-LD, etc. It would be difficult (and likely impractical) for them to edit a PDF.

Software can "understand" what is in JSON, JSON-LD, etc easier than a PDF.

RE: https://mastodon.social/@reiver/116597879302607072

More on a resume / CV on the Fediverse on Social Web.

Another option could be to use something like "JSON resume":

https://jsonresume.org/

https://github.com/jsonresume/resume-schema/blob/master/job-schema.json

It seems to be popular.

It isn't JSON-LD. Although I think it would be straightforward to translate it to JSON-LD, if that was desired.

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

@mariusor

Consider this use-case:

Someone wants to get hired on the Fediverse.

To build a "good" jobs oriented search for recruiters and hiring managers, I think it would be preferable to know if the phrase "software engineer" is a previous job title, or just appears in a random 'Note' on the Fediverse.

@reiver - there's an ontology called DOAC for this too - which I guess you could do as RDFa on a homepage, although it still has the complexity of being a formal ontology rather than an ad hoc schema.

I personally think it would be better to have flexible links from Fediverse profiles with machine readable semantics than to try to include everything in ActivityPub. A while back I was wondering about basic conventions for machine interpretable keys in the fields section.

@philcowans

I am considering both RDFa and Microdata (for putting these things into HTML).

The worry I have is — while I think Fediverse developers will happily work with JSON (including JSON-LD), they may be reluctant to try to extract data RDFa or Microdata out of HTML.

I suspect most of them will want to use pre-existing libraries for whatever their favorite programming-language is — and I don't know if those exist or not.

...

@philcowans

I am considering both RDFa and Microdata (for putting these things into HTML).

The worry I have is — while I think Fediverse developers will happily work with JSON (including JSON-LD), they may be reluctant to try to extract data RDFa or Microdata out of HTML.

I suspect most of them will want to use pre-existing libraries for whatever their favorite programming-language is — and I don't know if those exist or not.

...

My personal desire would be to create a format from scratch (because you are in control, you get 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

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

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

@reiver - this is great, thank you for putting it together.

I wonder if it is worth a pull request to the JSON Resume repo too, as that's likely a different community and it might make sense to bring them together. The same might be true if there are any general repositories in the RDF world.