@enkiv2 I remember FOAF! it's another reason library cards should come with shell accounts imo
Thanks for sharing.
Team Aardwolf will take this into consideration :)
@enkiv2 This as easily could have been called "The Web That Could Have Been". Which I think also captures what the problem was: that there weren't good authoring, publishing, or discovery tools built around FOAF (or much of the rest of the Web) that could be used by people who weren't web developers. Google showed a willingness to *use* machine-readable semantic information early on, but they weren't willing or perhaps able to build the authoring/publishing tools.
@enkiv2 Of course, Google never had an incentive to make the machine-readable stuff work well, because that would make it easier for others to compete with them. As long as Google is "organizing the world's information" in a way that very few others can (i.e. through heuristics and machine learning), it will be very difficult to compete with them.
(Related: FOAF, being embedded in HTML, requires updating otherwise-static files & frequently polling for changes. In the absence of a centralized authority, it means either a whole lot of independent scrapers or adding the facilities necessary to map and evaluate network graphs to browsers.)
@enkiv2 If the worst you can say about RDF is that it's XML, that doesn't seem so bad to me. Not that I'm a huge fan of XML, but editing files directly is for technically inclined folks. Others will use tools. And I don't think Postel's Law was ever intended to apply in cases of genuine ambiguity. Better to reject something another implementation might accept than to have two different implementations assign the same blob different meanings.
RDF isn't necessarily XML. Most of the dominant RDF serializations are XML-based because RDF was hot at the same time XML was hot, but there are dozens of them. (IIRC, JSON-LD is also an RDF serialization or has one?) Mostly, RDF bugs me because it's both weaker & more unnecessarily complicated than its non-webtech competitors.
The use of XML *is* my primary problem with FOAF, though. FOAF is a pretty limited subset of stuff, & there's no reason to embed it in HTML or XML. The smallest & most readable serialization format for RDF to support all its core features is a 3-column TSV (this is the format CMU NELL uses internally), & FOAF would be easier to read & write if you did it this way.
Une instance se voulant accueillante pour les personnes queers, féministes et anarchistes ainsi que pour leurs sympathisant·e·s. Nous sommes principalement francophones, mais vous êtes les bienvenu·e·s quelle que soit votre langue.
A welcoming instance for queer, feminist and anarchist people as well as their sympathizers. We are mainly French-speaking people, but you are welcome whatever your language might be.