#pdurbintantek: so JSON-LD doesn't solve any problems you have, I take it
#tantekpdurbin - I haven't see any description of any real world problems that *anybody* has that it solves (better than existing / simpler alternatives).
#tantekplenty of big orgs use overly complex technologies they don't need to be.
paulcp joined the channel
#tantekusually the result of some short term evangelism or personal pet project. however over time extra overhead from complexity tends to get it either neglected, shut down, or transitioned to something else.
#tantekalso, pdurbin - have you looked at the Google citation in that list? it's not even a use *on the web*
#tantekand speaking of such transitions, sometimes you see such big orgs take a minor step when they transition from something *more* complex to something still complex (but simpler). from that list, looks like some dumping RDFa to go to JSON-LD. which might also be a fashion statement.
#tantekthat is, fashion as in, "RDF*" has a reputation of being ugly (regardless of what it is attached to), and "JSON" has a reputation of the new hotness the kids like.
ireheart and paulcp joined the channel
#pdurbintantek: so if you're already invested in RDF... maybe look at JSON-LD? Otherwise, don't bother?
#tantekthat's pattern that can be seemingly discerned from that github link you pasted
#tantekI mean, I guess it keeps RDF/LD people employed?
hallettj joined the channel
#tantekfrom a broader perspective, it's not even clear that's worth the time to fight big (especially silo) companies adopting complex technologies - because all they're doing is saddling themselves with technical debt.
#tantekI should say, from an indieweb perspective, doesn't it help us (indieweb) look better in comparison if/when silos become less efficient of their own doing?
#tantekto put it in a more positive light, it makes more sense for us (indieweb) to focus on designing/implementing the simplest possible technologies directly necessary for our use-cases, and not worry about more complex approaches (or who claims to use them), except as priori art research (to avoid repeating mistakes).
#Loqitantek meant to say: to put it in a more positive light, it makes more sense for us (indieweb) to focus on designing/implementing the simplest possible technologies directly necessary for our use-cases, and not worry about more complex approaches (or who claims to use them), except as prior art research (to avoid repeating mistakes).
#pdurbintantek: thanks. I appreciate your perspective on all this
hallettj joined the channel
#tantekthanks pdurbin. yeah I keep trying to come back to working on, enabling actually personally (to each of us) useful use-cases. I think as long as we as a community keep focusing on that, we'll be more productive and empowering.
#tantekand on that note - I'm out for the night - have a good evening / weekend!
_6a68, scor, pfenwick, snarfed and paulcp joined the channel
#Loqibarnabywalters: jonnybarnes left you a message 1 day ago: all the articles on waterpigs.co.uk have the same published date and time, if you dont already know
#barnabywaltersnow to tidy up the code changes behind it and make some new content types
#barnabywaltersI’m consistently amazed by how speedy a CSV file index is
#barnabywaltersit’s just a pity there’s no ORDER BY equivalent — that’s going to end up being the thing which forces me to use a database in the end I think