Post
@ink @swib A question I'd hope you’d address: why bother with JSON-LD if you don’t care about RDF? JSON-LD is far more complex than either the RDF or the JSON data model. Learning everything you need to know to work with RDF is far easier than learning everything you need to know to work with JSON-LD.
If one “doesn't really care” about the underlying tech, as long as it “works” and is as easy to use as possible, then one is going to be quite receptive when the OpenAI sales rep comes calling…
@swib ok, the barrier to entry for a lightning talk is pretty low, so I added myself to the list: https://forum.swib.org/t/swib25-lightning-talks/937/7?u=edsu
Thanks for the encouragement & ideas @acka47 @dbs @dr0i @dsalo @hugh @julsraemy @lissertations @osma @rieyin you are excellent people!
@ink @swib A question I'd hope you’d address: why bother with JSON-LD if you don’t care about RDF? JSON-LD is far more complex than either the RDF or the JSON data model. Learning everything you need to know to work with RDF is far easier than learning everything you need to know to work with JSON-LD.
If one “doesn't really care” about the underlying tech, as long as it “works” and is as easy to use as possible, then one is going to be quite receptive when the OpenAI sales rep comes calling…
@rieyin I didn't mean to argue that there isn't value in understanding rdf and knowledge graphs more generally--there is! It gives me hope to hear you are continuing to help new practitioners and researchers understand these things.
I only would like to point out that a *teensy* bit more effort to make the vocabulary useful for people who are not using rdf native tooling, would go a long way for adoption...kinda like what happened with activitypub here in the fedi.
Thanks for the gut check, I don't want to be dismissive of other approaches, and ways of understanding.
@rieyin @ink @swib "why bother with JSON-LD if you don’t care about RDF? ". Because you satisfy two needs with one thing: 1) those who don't care about RDF and just want JSON (aka most web developers - and also backend devs in need of e.g. fast fulltext search engines) and 2) those who may find benefits in RDF. Or even both.
Reminds me on my #SWIB talk 2012 in behalf of @lobid : https://swib.org/swib12/slides/Christoph_SWIB12_117.pdf
@ink Feel free to call back to https://speakerdeck.com/dsalo/soylent-semantic-web-is-people
There's a remote chance somebody might even remember it.
@ink I like it. It might trigger some people to explore JSON-LD/Linked Open Usable Data with regard to #Bibframe where LOUD does not have much traction yet. Also, you can follow up nicely on @julsraemy's Tuesday talk "Linked Open Usable Data for Cultural Heritage: Community Building and Semantic Interoperability in Practice": https://forum.swib.org/t/linked-open-usable-data-for-cultural-heritage-community-building-and-semantic-interoperability-in-practice/1443 #swib25
@acka47 @ink In case, I have written an "extended transcript" or a short paper of my upcoming presentation, available here: https://doi.org/10.48620/92261 #LinkedData #swib25 #iiif #linkedart
@acka47 nice! I am definitely down to hear about what linkeddata looks like from the perspective of #sts and learn how that can inform the use of bibframe.
I think many people reject bibframe out of hand because, despite years of good work, not enough effort has been made to make it accessible to people who are working with data on the web.
@julsraemy @acka47 apologies, I didn't mean to stick an unwanted label on you. I worked in a DH lab for 8 years while doing my research, and came out the other side considering myself to be an #sts practitioner more than anything else, so I am projecting 😄 But yes, it is hard to get more #sts than Actor Network Theory!
@julsraemy @acka47 that's a good place to be!
A space for Bonfire maintainers and contributors to communicate
