15 ms·
Whatever Happened to the Semantic Web?
- rickdg 8y agoWe're getting there with CSS grid. First, we have to deal with the usual "You actually have to put div A inside div B in order to do X. Now which one gets the semantic tag? And what happens when we also need div C as a container to fix Y problem? "
- scabarott 8y agoIt's been replaced by the Decentralized Web as the latest fad (also with the backing of Tim Berners Lee). Let's see how far this one goes as well (though I'm really rooting for it to succeed).
- irrational 8y agoI thought the addition of elements to HTML5 like nav, main, article, etc. was the end result of the semantic web.
- mindcrime 8y agoNot really. That stuff does relate to "semantics" in the "Semantic Markup" sense, but it doesn't actually have much to do with the "Semantic Web" per-se. I mean, yeah, there is a weak sort of connection there, but when people talk about the "Semantic Web" they are mostly talking about RDF, whether it's encoded using RDF/XML, N3, Turtle, JSON-LD, or "other". And along with RDF are related technologies like OWL, inference engines that reason over a triplestore, etc.
- AznHisoka 8y agoWhat happened to the semantic web? Well... it happened. 1) We got schema data for Job Postings that companies like Google reads to build a job search engine. 2) We got schema for recipes. https://schema.org/Recipe https://schema.org/Recipe 3) We got the Open Graph schema for showing headlines/preview images in social networks. http://ogp.me/ http://ogp.me/ 4) We got schema for reviews: https://developers.google.com/search/docs/data-types/review https://developers.google.com/search/docs/data-types/review 5) We got schema for videos: https://developers.google.com/search/docs/data-types/video https://developers.google.com/search/docs/data-types/video 6) We got schema for product listings.
- deleted 8y ago[deleted]
- Grumbledour 8y agoI agree. While it didn't turn out to be the solution to all our Problems and not every webpage is chock full of semantic markup that anyone can scrape, there are still a lot of bits and pieces that stuck around. I always felt that one problem of more widespread adaption by users was missing software. There were and still are all these great microdata pieces out there, but can my browser save an address, add an event to my calender etc.? If these things were easily possible to even an inexperienced user, I think we would see much more semantic markup. But in the meantime, search engines and social networks sure have an easier time scraping information then before we talked about the semantic web.
- evrydayhustling 8y agoThese are definitely interesting things that semantic web influenced, but they're definitely not what semantic web aspired to be. The differences are a good laundry list of things that make standardized data models viable in the wild: They are organized around use cases, not data origins. They are opt-in, rather relying on distribution via some discovery standard. They are only used by subsets of the industry they serve, and that's ok. They aren't integrated with regulation in ways that force their use. (list continues)
- nine_k 8y agoI would rather see features on the web appear because users want them and expect them to work, and not because some regulation mandates their use.
- ghaff 8y agoLike a lot of things--though not everything--with the modern Internet (e.g. RageRank vs. hierarchical directories), some echo of the Semantic Web ended up happening mostly organically. The Semantic Web was a rather academic concept--think a library classification system for the Web. Tim Berners-Lee, among others, promoted it for a long time.
- 8y ago
- Mediterraneo10 8y agoWith regard to the first example, lowering volume of playing media when you get a phone call, I had that set up on my Nokia N900 a decade ago (Dbus on the N900 would trigger a script to ssh into my computer and pause mpd). Naturally this was a nerdy thing and not something accessible for the general public, but I mention it here just to encourage my fellow nerds to realize how much power they might already have with existing tools. The writer says that a business owner must add their office info to Google or Yelp and suggests there are no alternatives to such centralized repositories of information. However OpenStreetMap also has opening hours for businesses and medical practioners and that data is yours to process and play around with as you like. In fact, there is just so much data present now in OSM, we simply lack convenient end-user tools to extract and process it automatically.
- dwighttk 8y agoOSM is open, but it is still centralized. It doesn't come to your webpage and get the information about your hours from you (as far as I can tell)
- floren 8y agoA hybrid approach seems sensible: the OSM data contains a vetted/known URL for your business, then your client uses that URL to fetch the hours from the website. In a perfect world, anyway.
- rmc 8y agoOSM is a wiki, anyone can edit things, and there's wiki-like community review. So the owner of a business can add the details if they want, or someone walking past and looking at a sign can.
- dwighttk 8y agoRight but the semantic web idea is that the business owner puts the hours on their site and that lets everyone who wants to know the hours. No central site (OSM, google, yelp) required. I mean the person looking for the hours would probably go to one of those sites, but the hours wouldn’t be stored there.
- stickfigure 8y agoIt's really too bad that XML+XSLT didn't take off as the "replacement" for HTML. Before you recoil in horror hear me out... Web pages are a giant mess of content and presentation, and CSS doesn't really help much. XML is at least a way of describing data in a meaningful way. <book>, <author>, <chapter>, etc. XSLT provided a way of formatting XML in the browser. Sure the internet would still be full of inconsistent content structures, but it would still be way easier to machine read than the big mess of arbitrary <div>s and <p>s (most of which just display something blinky) that we have today.
- switchbak 8y agoThat probably would have been cleaner back in the day, but with rich UIs being what they are, I think JSON + client side templating logic is probably simpler (and composes well). I never had much luck using XSLT for anything non-trivial, and I imagine that experience isn't uncommon.
- rjsw 8y agoThe thing that makes this hard is the security model in browsers. You either keep the XSLT scripts in the same directory as the XML or need to turn off the check for cross-site scripts.
- rjsw 8y agoOk, how do you get XSLT that isn't in the same directory as XML to work in a browser ?
- lmm 8y agoThe two problems here are that XML/XSLT are horrible to work with (to the extent that you want to achieve what they were supposed to, you do it with the modern "single page app" style where you write javascript that retrieves data from an API and renders it into a UI) and that no-one actually wants to separate the content from the presentation anyway.
- arcbyte 8y ago
- jcelerier 8y agonot only the Semantic Web, but semantic anything. All the millions of taxpayer funds spent in semantic research...
- degyves 8y agoWe actually are on the semantic web for healthcare. See: http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interoperability http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interop... Other fields are moving towards semantic also
- etimberg 8y agoIt's used in power systems as well: https://en.wikipedia.org/wiki/Common_Information_Model_(electricity) https://en.wikipedia.org/wiki/Common_Information_Model_(elec...
- xamuel 8y agoI have some insight here because I did a postdoc working on anatomy ontologies in the UK. A big part of the problem with the semantic web is that lots of people in European academia use it as a collection of buzzwords for making grant proposals sexier, without understanding or caring what it actually means. Instead of saying, "Give us money to build a webpage", they say, "Give us money to expose metadata annotations using a RESTful API on the semantic web." I would prepare conference presentations where I was just filling slides up with BS to fill time. Devs from other universities (gotta check that international research box!) understood the technology even less than our team did. We provided them a tool for storing RDF triples for their webpage so they could store triples about anatomical relationships. They wanted to use said RDF store as their backend database for storing things like usernames and passwords. facepalm So you have all these academics publishing all this extremely important sounding literature about the semantic web, but as soon as you pry one nanometer deep, it's nothing but a giant ball of crap.
- evrydayhustling 8y agoYeah, semantic web really hacked the brains of academic-facing bureaucrats. It fell into this giant gap between what administrators don't know about business and what they don't know about technology... a gap big enough to shove every utopian idea about "an effortlessly integrated, data driven society" into. There's no such thing as "right" way to represent any given data stream, just ways that are more or less suitable to specific tasks and interests. That's why HTML failed as descriptive language (and has become fine-grained-formatting language), and it's why symantic web was doa.
- ghaff 8y ago>hacked the brains of academic-facing bureaucrats In all fairness, it was also promoted by legitimate academics including Time Berners-Lee. I actually saw him give a talk about it a number of years back for his Draper Prize speech.
- evrydayhustling 8y agoI remember his AAAI '07 talk where he laid into the audience for changing and reusing URLs. It made me really want to see this world he was imagining where millions of people using the web every which way agree to universally abide by a rule that makes their life a lot harder but makes it easier to reason about algorithms on the Web. Btw, I don't think this or failure of semantic web reflect badly on TBL. He is in a rare class of folks, along with Stallman, who can leave a bigger dent in the world while missing their ideals by a mile than most of is could if we got everything we wanted.
- augustocallejas 8y agoI thought Freebase [1] was the most promising "Semantic Web" technology, with a powerful query language (MQL) and an application platform called Acre [2]. I'm biased because I worked at Danny Hillis' adjacent company, Applied Minds, and met with the Freebase folks to talk about graph databases. I went to one of Freebase's Hack Days, and I could feel the energy around building applications on a semantically-aware global database. Unfortunately, they got acquired by Google, and Freebase eventually shut down. Thinking back now, I wonder if there would have been a business model in hosting private data graphs to subsidize the open source data. [1] - https://en.wikipedia.org/wiki/Freebase https://en.wikipedia.org/wiki/Freebase [2] - https://opensource.googleblog.com/2010/08/acre-open-source-platform-for-building.html https://opensource.googleblog.com/2010/08/acre-open-source-p...
- bordercases 8y agoThat really sucks. Being bought out by Google probably creates some implicit benefits to their search experience (likely with their topical breadcrumbs which returns widgets inside the search window giving a list of objects that match and near-match, like books by an author). But the acquisition prevents there from existing a service that can inspire a wider ecosystem on something like a federated platform. Blood monopolies, man
- heinrichhartman 8y agoSeems pretty clear to me that freebase was a thread to Google search. A semantic knowledge search with a powerful query language could replace a good chunk of free text google searches at least for power users. Makes sense for them to buy it and get rid of it that way.
- programminggeek 8y agoWeb API's happened instead.
- mindcrime 8y agoNothing "happened to" the Semantic Web. It's here, and it's growing in utility and capability as the technology matures. What isn't necessarily growing is understanding of what the Semantic Web really is, who it's for, how to use SemWeb capabilities, etc. I'll accept some responsibility for that last bit, as somebody who has been active in promoting, and advocating for the adoption of, SemWeb tech. I could do more / do a better job in that regard.
- EamonnMR 8y agoWell, now's as good a time as any to start! Let's say I wanted to throw a layer of semantic markup over an existing site - where would I go to figure out what schemas to use and how to use any given schema (it's been a while since I tried to SemWeb up a site.)
- mindcrime 8y agoThat's an interesting question, because it has a few assumptions baked into it. I'd love to write a long eassy on that right now, but I don't really have time. But to answer the core question, one good place to start familiarizing oneself with the various schemas that are available is: https://schema.org/docs/schemas.html https://schema.org/docs/schemas.html There's also a lot of good information at http://linkeddata.org/guides-and-tutorials http://linkeddata.org/guides-and-tutorials although I fear that site doesn't get as much love / attention as it should, and some of the links might be stale.
- arxpoetica 8y agoCare to share a concrete example of growth? Very curious onlooker here.
- mindcrime 8y agoWikidata would be an obvious example. They support SPARQL queries via the endpoint at https://query.wikidata.org/ https://query.wikidata.org/
- 8y ago
- jerven 8y agoWhat happened is that it became. We learned that we can't trust anything on the Web, but joly it is rather nice that you marked up your opening hours. In the end the semantic Web uptake was on the data not the meta data. Regards to the academic semweb grant story these same idiots are now chasing the cloud with out a clue. And before it was grid. For some fields there is uptake because it solves problems. But they hardly market themselves as semweb.it's more profitable to market they solve solutions.
- imhoguy 8y ago> Sean B. Palmer, [...], posits that the real problem was the lack of a truly decentralized infrastructure to host the Semantic Web on. To host your own website, you need to buy a domain name from ICANN, configure it correctly using DNS, and then pay someone to host your content if you don’t already have a server of your own. Exactly that was the lacking brick of true distributed linked (semantic) web which now has a chance to be fulfiled by IPFS/IPNS/IPLD or some upcoming standarized equivalent.
- thinelvis 8y agoBlogger/blogspot and RSS. We already had it, and still have it. It's not as pretty as Instagram, though. It's all over.
- gsnedders 8y agoThe RDF-based RSS versions never saw anywhere near as much adoption as the non-RDF based ones, though.
- ynniv 8y agoFor the same reason graphical programming languages are still unpoular, and the command line still rules: inputting normalized tags is many orders of magnitude harder than typing free text. Even on an adaptive touch interface. Even with tag completion. Even with a template to fill in. And when you do manage to input some well formed AST for your todo list, you're on an island by yourself, because everyone else is using free text (or their own, different tags or syntax). Because even if you have the same structure, you also need to use the same tags! What language are they supposed to be in?! They might as well be unique numbers unless you speak that language. It's facepalms all the way down.
- claydavisss 8y agoJavascript
- ilamont 8y agoI took TBL's Semantic Web class ("Linked Data Ventures") when I was a grad student in the fall of 2010. The class was well structured, and included an introduction to basic concepts and languages, lectures by people using it in production environments, and group projects. I wrote an account of the first class here (http://www.ilamont.com/2010/09/encounter-with-tim-berners-lee-and.html http://www.ilamont.com/2010/09/encounter-with-tim-berners-le...) and you can see a demo of the rudimentary educational app our team built here (http://www.ilamont.com/2011/03/challenges-of-creating-mobile.html http://www.ilamont.com/2011/03/challenges-of-creating-mobile...). As the title of the class indicates, the idea was to encourage the creation of real-world applications, and to that end the class groups were encouraged to have a mix of Course 6 and business school team members. At the time, it seemed that the Semantic Web was more of an academic/open source project rather than something that was widely embraced by developers, although some guest speakers did have working applications at their places of business. I think the hope was to seed the Cambridge startup ecosystem with SW/Linked Data examples that could encourage its spread into the real world. One of the teams in our class actually turned their project into a startup that was later acquired. I ran into one of the co-founders a few years later and asked if they continued to use the Semantic Web/Linked Data model that they had demoed in class. The answer: No, because it couldn't scale. That was an issue that was anticipated and discussed during the class, but there was hopeful talk that scaling issues would be resolved in the near future through various initiatives.
- sixdimensional 8y agoOn a related note, I'd also be interested to know how the semantic web was related to the rise of "knowledge graphs". That's another term that we heard about for a while (and clearly was implemented - Facebook, Google and Microsoft have them, for example), but I haven't heard much more publicly for a while.
- igorlev 8y agoWhat happened is that the technology spawned by the Semantic Web "fad" is now absolutely everywhere but it looks and works nothing like how people thought it would. Freebase, after being bought by Google became the foundation of the Google Knowledge Graph (aka "things not links"). This kicked off an arms race between all the major search providers to build the largest and most complete knowledge graphs (or at least keep pace with Google [1]). Instead of waiting for folks to tag every single page, it turned out that simple patterns cross referenced across billions of pages were good enough to extract useful knowledge from unstructured text. Some companies who had easier access to structured but dirty data (like LinkedIn and Facebook) were also able to utilize (and contribute to) all of that research by building their own knowledge graphs with names like the Social Graph and Economic Graph. Those in turn are helping to power a decent amount of their search and ad targeting capabilities as well as spawning some interesting work[2] All those knowledge graphs became a major part of Siri, Alexa and Google Home's ability to answer a wide range of natural language queries. As well as being pretty fundamental to a lot of tech like semantic search, improved ecommerce search and a bunch of intent detection approaches for chatbots. So yeah while the technology and associated research did turn out to be incredibly useful, adding fancier meta-tags to pages was not the direction that proved the most useful. [1] https://ai.google/research/pubs/pub45634 https://ai.google/research/pubs/pub45634 [2] https://research.fb.com/publications/unicorn-a-system-for-searching-the-social-graph/ https://research.fb.com/publications/unicorn-a-system-for-se...
- subhobroto 8y agoYup! I made an observation about monetizing the Semantic Web when playing the role of the data/ontology provider. You providea all the data while Siri, Alexa and Google Home gets the glory: https://news.ycombinator.com/item?id=18036041 https://news.ycombinator.com/item?id=18036041
- YeGoblynQueenne 8y agoThe problem with all this is that Google, Facebook, Linkedin et al are private companies, so their knowledge graphs are, well, theirs. The idea with the semantic web was that it would be open and it would belong to its users, not to some cabal of giant corporations that would use it to control the internets. That notion of openness and co-authorship of the knowledge on the web is now as dead as the parrot in the Pythons skit. And we're all much the worse for it- see all the debates about privacy and ownership of personal information and, indeed, metadata.
- bootsz 8y ago> Imagine a Facebook that keeps your list of friends, hosted on your own website, up-to-date, rather than vice-versa. Basically, the Semantic Web was going to be a web where everyone gets to have their own personal REST API, whether they know the first thing about computers or not. Sounds more or less like what the Urbit project (https://urbit.org/ https://urbit.org/) is trying to accomplish. Not an endorsement; it has serious flaws just like everything else. This is a very hard problem to solve. But I sure do hope someone manages to figure it out.
- dustingetz 8y agoStandards compliance is short-term expensive, someone like Facebook would have to make it cheap and/or dangle a carrot to make it worth it
- z3t4 8y agoAs it is now, the one who provides the data is the one who pays for everything (production, storage, compute, bandwidth), while middleman search engines take all the money. What if the middleman was required to pay a fee to index the data ? For example build money transactions into the HTTP protocol, where web sites could automatically ask for a small fee in order to "see more".
- jhasse 8y agoNo website would ask for the fee for SEO reasons.
- teddyh 8y agoIIRC, the (by some definition) original hypertext system, Xanadu, had this. It was supposed to (among many other things) keep track of who quoted who and how much and make sure everybody got paid fairly. It was much too complex and never got anywhere, and was completely replaced when the WWW came along with its dead simple model of URLs and HTML.
- tzury 8y agoRest API/JSON is the de facto industry standard for data exchange. No need to parse and extract data from semantic tags.
- deleted 8y ago[deleted]
- miket 8y agoThe main downfall of the Semantic web efforts are not technological, but due to a misalignment of incentives. Semantic web formats require content creators to annotate metadata for machines where webpages are intended for human readers. We think that the main way to achieve a practical semantic web is to have AI synthesize a Knowledge Graph from applying CV/NLP techniques to understanding all webpages. More about our project here: https://www.zdnet.com/article/the-web-as-a-database-the-biggest-knowledge-graph-ever/ https://www.zdnet.com/article/the-web-as-a-database-the-bigg...
- m34 8y agoEvery few months my mind circles around that topic. I think it won’t work if the underlying transport/presentation is „the web“ (i.e as in Web 2.0). Instead of decorating semantics/hints around the actual information mostly for SEO reasons it should work the opposite: using all available semantic hints and information bits there already are to create new information by aggregating and putting things in a new context. It adds value while building upon previous knowledge and allows information and context to be relevant indefinitely.
- beefheart 8y agoTry expressing not such a vague concept, but a concrete, real world application that actual stakeholders would be interested in investing into. You will find that: A) It's probably not that valuable B) None of the hard problems are technological
- m34 8y agoYou‘re right, I didn’t go into concrete detail. It‘s also hard to describe but the best analogy I can come up with: picture a CMS that actually is about _content_ instead of being tied to presentation. So e.g. writing an article about a certain historical event at a certain place consists of stringing all the information and relationships together. Bringing the correct pieces together eliminates errors and gives a piece of information more meaning when used in different contexts. Being able to correctly reference e.g. Venice, Italy instead of Venice LA, CA makes a huge difference when looking up time schedules, weather forecast, flight connections etc. Sure there are IATA codes for airports. Wouldn‘t it be great to mention Springfield in an article and having all information about that place (as well as all „backlinks“)? I also don‘t think it is a technology problem. However, I‘d like to think about this more in terms of DRY principle of information. There are publications on the web that solely exist to duplicate short-lived, relatively low quality information and putting ads on it. This may be acceptable for some consumer‘s point of view, but fails to create long-lasting contribution to mankind. Just dumping all bits we currently store into massive archives is possible but taking measures to keep the amount of „information archeology“ needed to understand this data feels the right thing to do. I‘ll iterate on that. Sorry if this reads even more confusing and esoteric, need some sleep now.
- MKolchin 8y ago"The Semantic Web will never work because when it works, you won't know it's the Semantic Web". Source: https://twitter.com/TomDeNies/status/653572860766781440 https://twitter.com/TomDeNies/status/653572860766781440
- newmana 8y agoThe Semantic Web was not XML but RDF. XML was the serialisation format.
- keepper 8y agoIt couldn't make money... One of the best examples of the semantic web was Daylife[1], and they wound up being "acquired" by two bit players[2] that figured out how to monetize things better.. :-/ [1] https://en.wikipedia.org/wiki/Daylife https://en.wikipedia.org/wiki/Daylife [2] https://techcrunch.com/2012/10/17/content-licensing-service-newscred-acquires-publishing-startup-daylife-appears-to-be-raising-more-funding/ https://techcrunch.com/2012/10/17/content-licensing-service-...
- subhobroto 8y agoYup! I made a few observations in my own comment. One being that there is no usable graph store you and I can use as of 2018. Another being about monetizing the Semantic Web when playing the role of the data/ontology provider. You provide all the data while the consumers (Siri, Alexa and Google Home) get the glory: https://news.ycombinator.com/item?id=18036041 https://news.ycombinator.com/item?id=18036041
- riku_iki 8y agoStore is easy, you put your triples to linearly scaleable cassandra. What you want is some fancy query language on top of that, right?
- beefheart 8y agoIt was the answer to a problem that nobody had, straight out of the dotcom bubble days where those answers could be sold as a business cases or for university grants. Basically any form of structured data, be it in XML or JSON, served through some channel of data, is everything people need. There is no benefit in further standardization. Simple, informal standards work better than monstrous specifications that nobody ever bothers to deal with properly. The most important part is reducing friction, that's why JSON is the most successful format despite its shortcomings.
- subhobroto 8y agoYup! I made a few observations in my own comment. One being that while a set of SPARQL Federated Queries would elegantly replace my assorted, custom collection of python scripts, scrapy and PhantomJS (slowly porting over to puppeteer) programs talking to Postgres, there is no usable graph store you and I can use as of 2018. Another being about monetizing the Semantic Web when playing the role of the data/ontology provider. The majority of your clients will want your data in relational formats than turtle/RDF files/format anyways. .. and if you do provide all the data, the consumers (Siri, Alexa and Google Home) get the glory: https://news.ycombinator.com/item?id=18036041 https://news.ycombinator.com/item?id=18036041
- bhuga 8y agoI was involved in the semweb community ~7 years ago, particularly the "RDF knowledge graph" end, and it's still a bewitching idea. A lot of smart people have/still do work in it, but it never reached any kind of success on the commercial (as opposed to academic) web, because: Serialization is not the hard part. The semweb community was obsessed with ontologies and OWL and schemas and taxonomies. If we can just break the problem down enough, the logic went, then systems will be able to infer new data about the world. But it never worked out that way. Eventually you just have to write some code. If you have to write code anyway, all the taxonomies and RDF in the world aren't helpful (indeed, they're almost certainly the least efficient way to model the problem). You just scrape the pieces of knowledge out of whatever JSON, HTML, or whatever else and glue them together with the code. You don't need the all-knowing semantic web, you just need a .csv of whatever tiny piece of it you care about. I have a distinct memory of trying to sell someone on the startup I was working on, a SPARQL database. I was pitching RDF as a way to model the problem, but eventually the person I was pitching just said "well, we can just outsource the scraping to our eastern european devs and put it all in one big table." I had a kind of "oh my" moment where I realized that the startup was never going to work: in the real world, you just write code and move on. Taking part in the great semantic knowledge base of the world doesn't matter and isn't needed. The other end of semweb, the "machine-readable web", more or less came to pass. schema.org, opengraph, and that sort of thing did 99% of what the semweb community wanted at 5% of the effort. The fact that all of that data is not in one giant database doesn't really matter to anyone; you rarely care about more than 2 or 3 web pages at once.
- pbhat 8y agoI worked for semantic web startup. The idea was we'd build private "knowledge graphs" for companies especially Pharma and Biotech. We experienced something similar to what you describe. We had a nice RDF generator and a query engine. The idea was we'd parse data from clients' DB and unstructured stuff and generate semantic graphs - whcih would be used for semantic graph apps like search and inferences. Looking back, it was never going to work. Most clients came to us for "analytics dashboard". They were happy with giant tables to power these dashboards (and they were right!)
- xchaotic 8y agoI was in the unfavourable position of trying to implement a commercial, performance product on top of a triple store with OWL inferencing. It was unworkable. A slightest error in the entire dataset was able to break inferencing elsewhere (butterfly effect), not to mention the performance. We worked out the performance, by adding layers of caching but the data correctness is in my view unrealistic.
- jandrewrogers 8y agoI worked on the Semantic Web, designing core data infrastructure, back when it was still hot. It disappeared because it had two fatal flaws: it was intrinsically non-scalable, both conceptually and technically. First, there is no universal "semantic". The meaning of things is ambiguous, and given a broad enough pool of people and cultural contexts, it becomes nigh impossible to converge on a single consistent model for individual terms and concepts in practice. A weak form of this is very evident in global data interchange systems and implementations, and the Semantic Web took this bug factory and dialed it up to eleven. In short, the idea of the Semantic Web requires semantics to be axiomatic and in the real world they are inductive and deeply contextual. (Hence the data model rule of "store the physics, not the interpretation of the physics.") That said, it is often possible to build an adequate semantic model in sufficiently narrow domains -- you just can't generalize it to everything and everybody. Second, implementation at scale requires an extremely large graph database, and graph database architectures tend to be extremely slow and non-scalable. They were back then and still are today. This is actually what killed the Semantic Web companies -- their systems became unusable at 10-100B edges but it was clear that you needed to have semantic graphs in the many trillions of edges before the idea even started to become interesting. Without an appropriate data infrastructure technology, the Semantic Web was just a nice idea. Organizations using semantic models today carefully restrict the models to keep the number of edges small enough that performance will be reasonable on the platforms available. The Semantic Web disappeared because it is an AI-Complete problem in the abstract. This was not well understood by its proponents and the systems they designed to implement it were very, very far from AI-Complete.
- openfuture 8y agoThis is why category theory is so important! It allows us to move between axiomatic systems by looking at the structure they have in common. I am convinced that the 'semantic web' will be accomplished via some easy to use version control meets functors gui program.
- jeremiem 8y agoYour first point is being worked on and there are a few upper ontologies being used. I find BFO [1] quite promising. I believe that we actually can generalize modelling. We have dictionaries filled with definitions, given enough time and discipline, I don't see why we couldn't make them formal. It's not an engineering problem though. [1] http://basic-formal-ontology.org/ http://basic-formal-ontology.org/
- dzink 8y agoThe financial incentives have become stronger for building walled gardens than a semantically open web. The semantic data has been more useful to giants that monetize it, than to millions of small publishers who are supposed to abide by the rules and maintain it. The issue is even bigger if you are listing valuable goods - from products, to jobs, to real estate/rental listings as a part of your marketplace or business. Aggregators like google can scrape and circumvent you, by taking away your users earlier in the acquisition chain, so why bother giving them your product graph.
- amelius 8y agoWho needs the semantic web when we have machine learning to extract the information we want?
- combatentropy 8y agoYes, Google surprised us all and made the semantic web unnecessary, even though I doubt it would have come to pass anyway. Consider a paper in 1998 by Sergey Brin, Larry Page, and others, that showed them finding the titles of books and the names of their authors amid the sludge of the World Wide Web: > We begin with a small seed set of (author, title) pairs [...]. Then we find all occurrences of those books on the Web [...]. From these occurrences we recognize patterns for the citations of books. Then we search the Web for these patterns and find new books. --- http://dis.unal.edu.co/~gjhernandezp/psc/lectures/MatchingMarketDesign/GooglePageRankAdwords/brin98what.pdf http://dis.unal.edu.co/~gjhernandezp/psc/lectures/MatchingMa... Starting with a seed of just five author-title pairs, their formula found thousands more.
- subhobroto 8y agoExtracting information is not the issue. Figuring out what it is is what the Semantic Web (or any good Ontology) helps solve. For a ML to provide that insight - requires the ML to have access to a good Ontology.
- miket 8y agoWe are trying to build a global knowledge graph from the web using AI at diffbot.com.
- danans 8y agoSomeone commented recently in another thread that you can make software from order (via languages) or from chaos (ML), or often a combination of the two. Perhaps determining "meaning" on the web is similar, where the synthetic "order" approach is semantic markup, but the analytical "chaos" approach is NLP, image object recognition, etc. I think you need both, since human produced content doesn't always follow discrete predefined categories, but also has patterns that can be pre-classified to solve real problems more easily.
- StillBored 8y agoThe only way this works is if there is some central agency enforcing and standardizing the tags/APIs. People (and programmers) are lazy, and ignorant. If its not in their face broken it frequently won't get fixed. I used to have html validator default enabled in firefox, which would point out HTML errors for every page I landed on. The percentage of web pages that had in your face HTML errors despite all the tools to check for broken HTML still didn't mean people put in the effort to assure their pages were error free. Basically, if the page rendered "correctly" in the developers browser and maybe another test browser or two, then it was job done.
- bitwize 8y agoIt was supplanted by AI and machine learning. Not only did these outbuzzword the Semantic Web, but as it turns out it's much easier to have a bunch of GPUs running CNNs to extract semantic info from the dirty data you have rather than attempting to cram that data into a well-specified ontology and enforcing that ontology on new incoming data.
- subhobroto 8y agoExtracting information is not the issue. Figuring out what it is is what the Semantic Web (or any good Ontology) helps solve. For a AI/ML to provide that insight - requires the ML to have access to a good Ontology. The reason is more nuanced. The main reason being money: https://news.ycombinator.com/item?id=18036041 https://news.ycombinator.com/item?id=18036041
- usrusr 8y agoOne core problem is that the attention economy of the conventional web has driven content creators so far away from the path of truthfulness that they would just ruin any truly distributed ontology with lies. As soon as you start actually consuming semantic data it becomes a protocol that begs to be "hacked".
- subhobroto 8y agoCompanies that don't have pressing revenue issues and a large petty cash allowance use it. A LOT. As a result, most BigCo and BigGovts use a lot of Semantic Web. There are full time employees at these places where all they do, full time, is write pages of documents about applying the Semantic Web to solving a problem. For example, thousands of man hours are spent by the U.S. Military on the Semantic Web every year. The reality for the rest of us: It does not make financial sense to build the Semantic Web. It's a chicken and egg problem. No one has been able to find a way to monetize the Semantic Web when playing the role of the data/ontology provider. You cant slap on an ad. You hand off the data and someone else renders it and slaps on an ad raking in all the money. If you are a data provider, it's much more practical going the traditional way: using relational databases and importing/exporting/feeding data using relational formats than turtle/RDF files. The majority of your clients will want your data in that format anyways. Designing, Building, Maintaining, Querying an Ontology takes a huge amount of expertise/resources. Even if you had all the money in the world to obtain the data: there currently exist, in single digits, with none of them being open source/free, capable/scalable triple stores that can store an Ontology/Graph that's dense enough to be meaningful while providing any level of practical turnaround time for queries. Individuals like you and I or small businesses just don't have this expertise/resources. We would be spending too much time writing our own graph database, carrying out alignments between entities from various datasets, looking at and correct bad data etc before we even get to what we originally set out to do. Instead, most of us scrape the data from HTML/REST+JSON; use taxonimies at best and custom code to do what we need to get done and call it a day. 12 years ago when I started learning about the Semantic Web, I envisioned we will be, in 2018, using software agents to make our lives simpler: 1. My software bot looks at my calendar to figure out my day's trip and queries the traffic data from the endpoints relevant to my route 2. It also tries to estimate when I will have time to eat and generate a list of nearby restaurants or fastfood locations depending on my available time 3. It would be able to query endpoints from gas stations relevant to my route to figure out whether and if I should fill up gas 4. If portions of my route has toll roads on it, to find out if I already have a pass and remind me to put it in my car ... A critical component of this happening would be support for federation: la SPARQL Federated Query. While SPARQL does support Federated Queries, no one has an incentive to support the feature because of the above mentioned monetization challenge. So is my vision in shambles? No. I still things done but now through an assorted, custom collection of python scripts, scrapy and PhantomJS (slowly porting over to puppeteer) programs talking to Postgres. There is not a single line of SPARQL involved in the whole pipeline and it does what I want it to do. ... just like everybody else, we are getting along just fine with our hacky solutions.
- zackmorris 8y agoThe $64,000 question is: how do you implement the semantic web without changing any HTML or backend code? Because the web is never going to change to adopt a semantic web standard. What we have now are facsimiles of the semantic web, things like Open Graph (which only provides the gist of page media, if that), proprietary search engine results, and proprietary APIs for walled gardens like Facebook. It's looking like machine learning is going to provide richer gists and then manually-coded directories will provide user interface controllers for those gists in Alexa and other agents. It's a far cry from a truly semantic web but most people won't know the difference. This is actually a pretty easy problem to solve, but to do it, we'd be running against the wind of capitalism. The semantic web is running behind the scenes at Google, ad agencies, even the NSA. Except they've built it around people's private data instead of publicly accessible documents. Just to throw some ideas out there, I would start with the low-lying fruit: we need a fully-indexed document store that doesn't barf on mangled data. We need a compelling reason for people to have public profiles again (or an open and secure web of trust for remote API access). We need annotated public relationship graphs akin to ImageNet or NIST for deriving the most commonly-used semantics (edit: DBpedia is a start). Totally doable, but developers gotta pay rent.
- anon1253 8y agoidentical title https://joelkuiper.eu/semantic-web https://joelkuiper.eu/semantic-web
- ppeetteerr 8y agoI am surprised that the author did not mention the semantic web we did get. It's in his source, after all. If you look at the header of the page, you'll see the lines below. Sure they are not the utopian version of the semantic web we were promised. Instead, it's even better: it's the pragmatic semantic web we need: <!-- Twitter --> <meta name="twitter:card" content="summary" /> <meta name="twitter:site" content="@TwoBitHistory" /> <!-- OpenGraph --> <meta property="og:image" content="https://twobithistory.org/images/logo.png" /> <meta property="og:url" content="https://twobithistory.org/2018/05/27/semantic-web.html" /> <meta property="og:title" content="Whatever Happened to the Semantic Web?" /> <meta property="og:description" content="In 2001, Tim Berners-Lee, inventor of the World Wide Web, published an article in Scientific American. " />
- brennebeck 8y agoThe author specifically mentioned opengraph, or are you referencing something else?
- ppeetteerr 8y agoThe author does but as an aside. I think OpenGraph is the practical application of a more utopian semantic web and it deserves a lot more recognition.
- tokyodude 8y agoThe Semantic Web would never have worked IMO. All you have to do is take a look at Soundcloud's tags. People will tag their songs with whatever tags they think will help their music get hits.
- partycoder 8y agoAnd VRML.
- gibsonf1 8y agoThere is great power in rdf graph databases (Allegrograph) and the rapidly growing collection of valuable ontologies https://lov.linkeddata.es/dataset/lov/ https://lov.linkeddata.es/dataset/lov/ The barrier to entry is thinking in “graph” instead of relational dB, which is a big cultural change, and then shifting focus and attention to the information science of building valuable ontologies. Once you make the leap, it’s hard to go back - it’s an order of magnitude productivity gain.
- mickael-kerjean 8y agoThe potential of the semantic web is massive. It's hard to understand why it hasn't been a massive game changer. I remind a few years ago making crazy query to answers questions that still today has no equivalent like: Find companies CEO that has less than 100k employees and was created before Neil Amstrong walked on the moon. The winner take all approach we have today with all those sillos doesn't benefit human kind in any way.
- nchuhoai 8y agoI just had to try this with Wikidata. Unfortunately did not work well https://query.wikidata.org/#SELECT%20%3FpresLabel%20%3FcompanyLabel%20%3FfoundingTime%20WHERE%20%7B%0A%20%20%3Fpres%20wdt%3AP31%20wd%3AQ5.%0A%20%20%3Fpres%20p%3AP39%20%3Fposition_held_statement.%0A%20%20%3Fposition_held_statement%20ps%3AP39%20wd%3AQ484876.%0A%20%20%3Fposition_held_statement%20pq%3AP642%20%3Fcompany.%0A%20%20%3Fcompany%20wdt%3AP1128%20%3Femployees.%0A%20%20%3Fcompany%20wdt%3AP571%20%3FfoundingTime.%0A%20%20%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22.%20%7D%0A%20%20FILTER%28%3Femployees%20%3C%20100000%29%0A%20%20FILTER%28YEAR%28%3FfoundingTime%29%20%3E%201965%29%0A%0A%7D https://query.wikidata.org/#SELECT%20%3FpresLabel%20%3Fcompa...
- narrator 8y agoThe semantic web relies on people not lying. Unfortunately, meta tags were instantly filled with seo spam as soon as they were implemented. It's a trusted client approach to data integrity.
- jackcosgrove 8y agoThe web is just a subset of the internet, and a shrinking one as a share. More communication over the internet is between client-server apps rather than between browsers and other open standards, as was envisaged when the web started. JavaScript apps and mobile apps are tightly coupled with their services. Although HTTP has proven resilient, HTML/XML has not. XML's verbosity that enables semantic meaning is exactly its undoing compared to JSON. When meaning is built into both client and server, communication needs to be skinny not rich.
- gideon_b 8y agoInteresting, this post implements the og tags for social sharing (image and description) but skips the full og:article tags with author, date etc. Edit: https://search.google.com/structured-data/testing-tool/u/0/#url=https%3A%2F%2Ftwobithistory.org%2F2018%2F05%2F27%2Fsemantic-web.html https://search.google.com/structured-data/testing-tool/u/0/#...
- tonyoconnell 8y agoIf you ask that question in 5 years perhaps the answer will be that it came alive with AI. As AI becomes more important so should the Semantic Web since it will provide data to train the machines.
- planck01 8y agoI worked on the Semantic Web. It has so many fatal flaws, that I am amazed in hindsight that I didn't see them back then. Berners-Lee was successful with the Web because it was not an academic idea like Nelson's and Engelbart's hypertext, but it was a pragmatic technology (HTTP, HTML and a browser) that solved a very practical problem. The semantic web was a vague vision that started with a simplistic graph language specification (RDF) that didn't solve anything. All the tools for processing RDF were horrendous in complexity and performance and everything you could do with it could typically be solved easier with other means. Then the AI-people of old came on board and introduced OWL, a turn for the worse. All the automatic inference and deduction stuff was totally non-scalable on even toy examples, let alone web scale. Humans in general are terrible in making formal ontologies, even many computer science students typically didn't really understand the cardinality stuff. And how it would bring us closer to Berners-Lee vision? No idea. Of course, its basic assumptions about the openness, distributedness and democratric qualities of the Web also didn't hold up. It didn't help that the community is extremely stubborn and over confident. Still.They keep on convincing themselves it all is a big success and will point at vaguely similar but successful stories built on completely different technology as that they were right. I think this attitude and type of people in the W3C also has lead to the downfall of the W3C as the Web authority.
- sacado2 8y agoThere are different flavors of OWL nowadays. Some of them are especially dedicated to reason on huge volumes of data (polynomial algorithms), although they are not very expressive. Some are more expressive, but don't scale very well. Some are incredibly expressive, but are undecidable, so you can only use them as a formal representation of a domain, not something you can reason from. The practice in the community is to choose a fragment of OWL/description logic that fits your needs. Different tools for different uses. In practice I'm especially fond of the simplest languages, just a little more expressive than a database schema or an UML class diagram, as they are easy to describe things with and yet very useful, with lots of efficient algorithms to infer new things.
- dalbasal 8y agoI agree on the problem with abstract goals. I could never really thought understand what it was going to do in specific terms, going from a "Programs could exchange data across the Semantic Web without having to be explicitly engineered to talk to each other" to some specific cases that seemed useful. Spolsky had a great blog about this ki d of thing. CS people looking at napster, overemphasizing the peer-to-peer aspects and endeavouring to generalized it. Generalising is what science does, so the drive was there. Generalising a solution is... It can lead you down path to solutuon-seeking problem. The web is also hard. Lots of chicken-egg problems to solve. When TBL released www he had a browser, server and web pages that you could use right now. The "standards" existed for a non abstract reason. On criticisms of W3C... idk. The have an almost impossible job. The world's biggest companies control browsers. Standards are very hard to change. Very hard network effect problems, people problems. Enourmous economic, political & ideological interests are impacted by their decisions. You could say that they not have been involved with the project until it was much more mature and they could decide whether or not to include it. That said, if they were those sorts of people I stead of academic... I'm not sure if that's better. So.e things just don't work out.
- sacado2 8y agoMixing semantic web techs with ML is hot in the domain right now. Because ML solves problems symbolic approaches cannot solve (dealing with huge amounts of raw, poorly structured data) and symbolic approaches solve problems ML cannot (dealing with logical reasoning and inferences, like in the query "give me all cities of more than 1 million inhabitants that are less than 300km away from Paris, sorted from southernmost to northernmost").
- YeGoblynQueenne 8y agoThis is why we can't have nice things. When someone (sure, W3C- anyone) tries to, you know, design stuff before it's built, everyone whines and complains about how it's all too "mathy", how the standard is bloated so we shouldn't have any standards at all, how the standard is not good for "real work", etc etc. Then, since all those hard-working programmers are, allegedly, too dumb to get their heads around XML (XML! Oh, the complexity!), RDF and OWL, along come the big companies and crate their own, de facto standards. So now, if you want to do work, you have to abide by those standards, whether you like it or not and you don't even get to influence them, because they're not some open web committee that you can badger about the quality of their standards, but closed, walled-up conglomerates that don't care how nice the web is, only that they can control it. Not to mention, the end result is a hairball alright, a big pile of tangled up hacky, ad-hoc APIs, bashed together as fast as possible, "to get things done quickly". ... and everyone is still using XML anyway.
- YeGoblynQueenne 8y agoHN, sorry for the rant. RDF was such a good idea, especially as human-readable, human-editable turtle. There was a lot of clunkiness there, in the W3C standard, but, W3C standards are made to be openly debated and revised. Facebook APIs, on the other hand - not so much.
- idoitforreal 8y agoThe Semantic Web is alive and well and doing great, thank you very much. You should drop by some time and check out the real thing. Unfortunately, hype in any field will attract losers and opportunists, but why focus on the negative? Never mind academia: Some of the world's largest companies are investing serious money in semantic-web approaches to get a grip of their information resources. You won't see it because it's mostly behind the scenes, in intranets and infrastructure that feeds data to your nice shiny restaurant recommender, or whatever. The software stack is getting better and more robust-- you can do things quickly with billions of triples that would take you weeks of development to program in a non-trivial relational database environment. The Semantics 2018 conference just took place in Vienna. It was heavy in industry presence and there was a lot of money going around. These guys guys don't give money outside the company unless they're going to get value for it. So yes, reports of the imminent arrival of the Semantic Web ten years ago were greatly exaggerated. But if you're looking for a topic with an amusingly clueless commentariat, you'll do better to google "PHP object-oriented programming" (or just "hacker", for that matter).
- deleted 8y ago[deleted]
- jbottoms 8y agoThis I Know Is True: 1. There are few Internet historians. It is difficult and thankless work that doesn't pay well. And too much of the information is lost to history, or can protested by gain-saying, even the true bits. 2. The first browser, Silversmith, was released in 1987. [http://www.linfo.org/browser.html http://www.linfo.org/browser.html] (thanks BELUG). It worked in English and grew out of my work on the Association of American Publisher's Electronic Manuscript project, the first U.S. electronic publishing project using tags outside of IBM's product offerings. At the time I had been on the Internet since 1972 and I was tired of typing 128.24.67.xxx. (There was a phone book of IP addresses at the time and I was listed in it for work I was doing on satellite image processing on Illiac.) 3. The second browser, a version of Silversmith, was designed for Old Norse for a researcher and it used Norse runes for the display; the controls were in Roman characters. 4. The third browser, a version of Silversmith, was a semantic browser for a U.S. military application. It was successful as far as I know. 5. The fourth browser, Erwise, [http://www.osnews.com/story/21076/The_World_s_First_Graphical_Browser_Erwise http://www.osnews.com/story/21076/The_World_s_First_Graphica...] came about after I gave a paper on Silversmith in Gmunden, Austria in 1988. Erwise worked in the Finnish language. I understand that TimBL looked at it before developing the W3c browser but decided against using it because the comments were in Finnish. 6. I have seen various dates for the browsers from TimBL and MarcA, but they were at least a few years after Silversmith. We can call them the 5th and 6th, but I'm not sure of the ordering. Both of these browsers were based on the earlier AAP Book tag set. 7. Some of my work on Silversmith grew out of Ted Nelson's work on the Alexandria (Xanadu) project. Much of his work has still not been implemented, but that may soon change. 8. Ted developed hypertext controls for printed documents. In that approach when you finished reading a child section a return page number was there to show you where you left off. 9. I developed the first eHypertext system for networks that would link you back to your source document that you came from by pressing the ESC key. In Silversmith you could link between text, images, sound and semantic information. 10. Silversmith is a scalable system. Please observe that just because you don't know how that is done, does not mean it cannot be done. That was what was told me about browsing and searching earlier also. 11. At the time Silversmith was developed, it was understood that VC's would not talk to you without you having a working product. Once I had it working, I found that VC's would still not talk to you. I talked with about a dozen Boston VC's. They would not even sit for a demonstration. I did a demonstration for the ACM in 2007 (thanks PeterG). That is the nature of tools and the bane of toolsmiths, no one wants to pay for tools. I have a recurring nightmare of the yokel who returned his anvil to the smithy saying, "It doesn't work. I can't use it to make beautiful horseshoes like Kevin does, and he has the same anvil. There's something wrong with this one." With Silversmith I lost a competition among 80 vendors for a search application, when none of the others even had an application. One competitor even called me and demanded all my specs and internal design documents. That is largely why you will not find any published information on Silversmith. 12. I can't tell you how many times I have been schooled on programming languages. "You should program that using ThinkC/ObjectiveC/SmallTalk/the X-System." "You need to switch to Ruby-On-Rails/Perl/Python/Awk, that's the way to do it." People, it's not the language, it's the data structures and the code that is important. And, enough with "speed is important." We are all using supercomputers and they will never be fast enough. 13. Silversmith predated the W3c work by several years, that is why I prefer to use the term "semantic web" (lower case) to distinguish it from the W3c term. I discussed the term "web" with Ted and he agreed that was in use earlier before the WWW. 14. Monitizing a tool is an interesting discussion. No one wants to pay $1 every time they pick up a hammer. But for a cabinetmaker, his/her primary tool is the table saw. This means that they are more than willing to pay on a regular basis for maintenance. They must, it is their livelihood, and the manufacturer is going to make money on that maintenance. He does not expect to be able to charge the cabinetmaker a portion of his sales. That is not how that market works. To me, even razor and blades are not fully monitized if you sharpen your own blades. 15. Semantic work is "path dependent" work. Once you start down a certain path it becomes very difficult to retrace your steps. I used to be critical of academics who "sold out" to the W3c vision, but now I realize that for the most part they are trying to provide what the industry wants and uses. 16. Work on Silversmith continues and I'm pleased to say that it is progressing well. The next version will assist in finding and using knowledge in a more conceptual way.
- deleted 8y ago[deleted]
- auct 8y agoThe author of semantic web forgot about money. What is the profit of website owner if he freely shares markup?
- cody-burleson 8y agoI don't think the use of Semantic Web technologies presupposes open data. Linked Data doesn't have to be Linked Open Data. One could create services that adhere to the standards while still monetizing them.