Linked Data in HTTP Headers rather than in JSON (i.e., JSON-LD), etc
⁂
Many Fediverse servers will give you different content depending on the "Accept" header in the HTTP request.
If "application/activity+json" you get ActivityPub/ActivityStreams JSON-LD metadata. If something else, you get actual file/payload.
If we encoded Linked Data as HTTP headers (key-value pairs), we could include the Linked Data with the actual file/payload.
An alle auf https://lsbt.me
Unsere Instanz ist auf der aktuellsten, stabilen Glitchsoc Version. Damit sind (unter Anderem) folgende kritische Sicherheitslücken behoben und geschlossen:
Viel Spaß! 🙂
LG Christin
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
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
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
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://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/116597841178183282
There is also the other question of — would the resume / CV be JSON-LD.
On one hand, if it was in JSON-LD, it would make it machine-legible similar to ActivityPub.
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.
It feels like user-experience is fighting with JSON-LD based machine-legibility.
How could you represent a resume / CV on the Fediverse and Social Web? Where would you put it? Etc?
I think it is tempting to put the whole resume in the Actor document.
But, it is probably better for the Actor document to point (rather than include) it. And, have the resume / CV live somewhere else.
It should probably be done in a way that let's people have multiple resumes / CV. For example, for different roles / career tracks, etc.
In ActivityPub, these are all equivalent:
"type":"Banana"
"type":["Banana"]
"type":{"＠id":"Banana"}
"type":[{"＠id":"Banana"}]
"type":{"id":"Banana"}
"type":[{"id":"Banana"}]
"＠type":"Banana"
"＠type":["Banana"]
"＠type":{"＠id":"Banana"}
"＠type":[{"＠id":"Banana"}]
"＠type":{"id":"Banana"}
"＠type":[{"id":"Banana"}]
@reiver ⊼ (Charles) 
Todd Sundsted
🏳️⚧️ Christin Löhner 🏳️🌈
