Is there already an ActivityPub vocabulary for job openings, or cvs?
-
Is there already an ActivityPub vocabulary for job openings, or cvs?
I'm trying to make my CV-webpage more visible, and also create a job-bot, that everyone can set up with their sources, and queries.
Obviously the idea is, to help people find jobs, and fill vacancies, without having to resort to a centralized network, like e.g. LinkedIn.
I'm aware of these efforts, though they're not ActivityPub related:
https://microformats.org/wiki/job-listing
https://microformats.org/wiki/h-resume -
Is there already an ActivityPub vocabulary for job openings, or cvs?
I'm trying to make my CV-webpage more visible, and also create a job-bot, that everyone can set up with their sources, and queries.
Obviously the idea is, to help people find jobs, and fill vacancies, without having to resort to a centralized network, like e.g. LinkedIn.
I'm aware of these efforts, though they're not ActivityPub related:
https://microformats.org/wiki/job-listing
https://microformats.org/wiki/h-resumeYou could, for example, use h-resume with ActivityPub.
ActivityPub is, in some ways, just another JSON-LD name-space.
Just use h-resume as another JSON-LD name-space along with ActivityPub.
-
You could, for example, use h-resume with ActivityPub.
ActivityPub is, in some ways, just another JSON-LD name-space.
Just use h-resume as another JSON-LD name-space along with ActivityPub.
Yes, as a starting point, that's what I thought as well. Just if there already would have been sinething, I wouldn't try and reinvent the wheel.
One issue with blindly adopting #h-resume is, that in an #ActivityPub context, you usually don't just state "here is my resume", but also e.g. "I have a new job", which then is an update to your resume. A use case, that never existed for h-resume.
So there's still work to do. But it's definitively a good start.
-
Yes, as a starting point, that's what I thought as well. Just if there already would have been sinething, I wouldn't try and reinvent the wheel.
One issue with blindly adopting #h-resume is, that in an #ActivityPub context, you usually don't just state "here is my resume", but also e.g. "I have a new job", which then is an update to your resume. A use case, that never existed for h-resume.
So there's still work to do. But it's definitively a good start.
Regarding:
"but also e.g. "I have a new job""You could either do that with a custom Object type.
Or, using an existing Object type โ such as Note, or one of the others.
-
Regarding:
"but also e.g. "I have a new job""You could either do that with a custom Object type.
Or, using an existing Object type โ such as Note, or one of the others.
Are you thinking of coding something for this?
-
Are you thinking of coding something for this?
I'm still in the phase of finding out, if there might already be all the tools available, but it seems, I won't get around writing at least some code for it.
I'll probably start extending an existing AP implementation, or using a library, instead of writing everything from scratch. But nothing is set in stone yet. Do you have any suggestions?