Goofed Home

@thisismissem

"I don't think that would be accurate at all, in terms of what I presume most might think."

That was in reference to Elena's comment about being viewed as a team player... and nothing else.

As for "my memories failing me...", I was recalling from memory what I read years ago and recollected as Eugen's comments on why he had chosen to work on ActivityPub and Mastodon. I'm not a member of the board, nor do I have access to info on those events.

@thisismissem Could be. But I'd also expect URLs like this for Ghost Authors to be resolvable in AP Clients and/or Mastodon. https://blog.identity.foundation/author/dif/

@thisismissem Ah, you are assuming that the dev is also doing the data modeling. Gotcha, makes sense for Indie-Devs or small ventures.

Still, what you describe is not particular to JSON-LD. Devs can simply store their JSON objects in a Pod.

In my experience, the "confused dev" that you described above occurs when the devs are forced to use JSON-LD without understanding the basics of RDF. Proper on onboarding is crucial here, tooling like LDO and similar do exist to ease LD development ...

@thisismissem just stumbled over your comment here.

Why did the developers need to come up with a "schema" in the first place? Proper data modeling is hard (as you say too)

Devs can just define their JSON objects and store them on a Pod, and read them from the Pod in their app. You _can_ simply ignore the LD part here. (My students always do that first when they are already used to web dev)

Doing data modeling for LD (which we should! :) ) just gives you more features from the RDF world, no?