Semantic Web · Lablypedia

To enable the encoding of semantics with the data, technologies such as Resource Description Framework (RDF) and Web Ontology Language (OWL) are used. These technologies are used to formally represent metadata. For example, ontology can describe concepts, relationships between entities, and categories of things. These embedded semantics offer significant advantages such as reasoning over data and operating with heterogeneous data sources. These standards promote common data formats and exchange protocols on the Web, fundamentally the RDF. According to the W3C, "The Semantic Web provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries." The Semantic Web is therefore regarded as an integrator across different content and information applications and systems.

History

The term was coined by Tim Berners-Lee for a web of data (or data web) that can be processed by machines—that is, one in which much of the meaning is machine-readable. While its critics have questioned its feasibility, proponents argue that applications in library and information science, industry, biology and human sciences research have already proven the validity of the original concept.

The idea of adding semantics to the Web predates the term itself. Berners-Lee discussed the need for semantics in the Web at the first International World Wide Web Conference in 1994. In 1998, he published a design document titled "Semantic Web Road map", outlining the architecture for a web of machine-processable data. The first patent for the creation of a semantic web was filed by Amit Sheth et al. on 30 October 2001.

Berners-Lee originally expressed his vision of the Semantic Web in 1999 as follows:

I have a dream for the Web [in which computers] become capable of analyzing all the data on the Web – the content, links, and transactions between people and computers. A "Semantic Web", which makes this possible, has yet to emerge, but when it does, the day-to-day mechanisms of trade, bureaucracy and our daily lives will be handled by machines talking to machines. The "intelligent agents" people have touted for ages will finally materialize.

The 2001 Scientific American article by Berners-Lee, Hendler, and Lassila described an expected evolution of the existing Web to a Semantic Web. In 2006, Berners-Lee and colleagues stated that: "This simple idea…remains largely unrealized". In 2013, more than four million Web domains (out of roughly 250 million total) contained Semantic Web markup.

7 more chapters are free with a Lably account.

Example

In the following example, the text "Paul Schuster was born in Dresden" on a website will be annotated, connecting a person with their place of birth. The following HTML fragment shows how a small graph is being described, in RDFa-syntax using a schema.org vocabulary and a Wikidata ID:

<span id="mwdw"></span><span class="p" id="mweA"><</span><span class="nt" id="mweQ">div</span> <span class="na" id="mweg">vocab</span><span class="o" id="mwew">=</span><span class="s" id="mwfA">"https://schema.org/"</span> <span class="na" id="mwfQ">typeof</span><span class="o" id="mwfg">=</span><span class="s" id="mwfw">"Person"</span><span class="p" id="mwgA">></span> <span class="p" id="mwgQ"><</span><span class="nt" id="mwgg">span</span> <span class="na" id="mwgw">property</span><span class="o" id="mwhA">=</span><span class="s" id="mwhQ">"name"</span><span class="p" id="mwhg">></span>Paul Schuster<span class="p" id="mwhw"></</span><span class="nt" id="mwiA">span</span><span class="p" id="mwiQ">></span> was born in <span class="p" id="mwig"><</span><span class="nt" id="mwiw">span</span> <span class="na" id="mwjA">property</span><span class="o" id="mwjQ">=</span><span class="s" id="mwjg">"birthPlace"</span> <span class="na" id="mwjw">typeof</span><span class="o" id="mwkA">=</span><span class="s" id="mwkQ">"Place"</span> <span class="na" id="mwkg">href</span><span class="o" id="mwkw">=</span><span class="s" id="mwlA">"https://www.wikidata.org/entity/Q1731"</span><span class="p" id="mwlQ">></span> <span class="p" id="mwlg"><</span><span class="nt" id="mwlw">span</span> <span class="na" id="mwmA">property</span><span class="o" id="mwmQ">=</span><span class="s" id="mwmg">"name"</span><span class="p" id="mwmw">></span>Dresden<span class="p" id="mwnA"></</span><span class="nt" id="mwnQ">span</span><span class="p" id="mwng">></span>. <span class="p" id="mwnw"></</span><span class="nt" id="mwoA">span</span><span class="p" id="mwoQ">></span> <span class="p" id="mwog"></</span><span class="nt" id="mwow">div</span><span class="p" id="mwpA">></span>

The example defines the following five triples (shown in Turtle syntax). Each triple represents one edge in the resulting graph: the first element of the triple (the subject) is the name of the node where the edge starts, the second element (the predicate) the type of the edge, and the last and third element (the object) either the name of the node where the edge ends or a literal value (e.g. a text, a number, etc.).

<span id="mwsg"></span> <span class="nn" id="mwsw">_</span><span class="p" id="mwtA">:</span><span class="nt" id="mwtQ">a</span> <span class="nv" id="mwtg"><https://www.w3.org/1999/02/22-rdf-syntax-ns#type></span> <span class="nv" id="mwtw"><https://schema.org/Person></span> <span class="p" id="mwuA">.</span> <span class="nn" id="mwuQ">_</span><span class="p" id="mwug">:</span><span class="nt" id="mwuw">a</span> <span class="nv" id="mwvA"><https://schema.org/name></span> <span class="s" id="mwvQ">"Paul Schuster"</span> <span class="p" id="mwvg">.</span> <span class="nn" id="mwvw">_</span><span class="p" id="mwwA">:</span><span class="nt" id="mwwQ">a</span> <span class="nv" id="mwwg"><https://schema.org/birthPlace></span> <span class="nv" id="mwww"><https://www.wikidata.org/entity/Q1731></span> <span class="p" id="mwxA">.</span> <span class="nv" id="mwxQ"><https://www.wikidata.org/entity/Q1731></span> <span class="nv" id="mwxg"><https://schema.org/itemtype></span> <span class="nv" id="mwxw"><https://schema.org/Place></span> <span class="p" id="mwyA">.</span> <span class="nv" id="mwyQ"><https://www.wikidata.org/entity/Q1731></span> <span class="nv" id="mwyg"><https://schema.org/name></span> <span class="s" id="mwyw">"Dresden"</span> <span class="p" id="mwzA">.</span>

The triples result in the graph shown in the given figure.

One of the advantages of using Uniform Resource Identifiers (URIs) is that they can be dereferenced using the HTTP protocol. According to the so-called Linked Open Data principles, such a dereferenced URI should result in a document that offers further data about the given URI. In this example, all URIs, both for edges and nodes (e.g. http://schema.org/Person, http://schema.org/birthPlace, http://www.wikidata.org/entity/Q1731) can be dereferenced and will result in further RDF graphs, describing the URI, e.g. that Dresden is a city in Germany, or that a person, in the sense of that URI, can be fictional.

The second graph shows the previous example, but now enriched with a few of the triples from the documents that result from dereferencing https://schema.org/Person (green edge) and https://www.wikidata.org/entity/Q1731 (blue edges).

Additionally to the edges given in the involved documents explicitly, edges can be automatically inferred: the triple

<span id="mw4A"></span> <span class="nn" id="mw4Q">_</span><span class="p" id="mw4g">:</span><span class="nt" id="mw4w">a</span> <span class="nv" id="mw5A"><https://www.w3.org/1999/02/22-rdf-syntax-ns#type></span> <span class="nv" id="mw5Q"><http://schema.org/Person></span> <span class="p" id="mw5g">.</span>

from the original RDFa fragment and the triple

<span id="mw6g"></span> <span class="nv" id="mw6w"><https://schema.org/Person></span> <span class="nv" id="mw7A"><http://www.w3.org/2002/07/owl#equivalentClass></span> <span class="nv" id="mw7Q"><http://xmlns.com/foaf/0.1/Person></span> <span class="p" id="mw7g">.</span>

from the document at https://schema.org/Person (green edge in the figure) allow to infer the following triple, given OWL semantics (red dashed line in the second Figure):

<span id="mw9A"></span> <span class="nn" id="mw9Q">_</span><span class="p" id="mw9g">:</span><span class="nt" id="mw9w">a</span> <span class="nv" id="mw-A"><https://www.w3.org/1999/02/22-rdf-syntax-ns#type></span> <span class="nv" id="mw-Q"><http://xmlns.com/foaf/0.1/Person></span> <span class="p" id="mw-g">.</span>

Background

The concept of the semantic network was used in the 1950s and 1960s by researchers such as the Richard H. Richens, cognitive scientist Allan M. Collins, computational linguist M. Ross Quillian and psychologist Elizabeth F. Loftus to represent semantically structured knowledge, both conceptually and in computer systems.

The term "Semantic Web" was coined by Tim Berners-Lee, the inventor of the World Wide Web and director of the World Wide Web Consortium ("W3C"), which oversees the development of proposed Semantic Web standards. He defines the Semantic Web as "a web of data that can be processed directly and indirectly by machines". The Semantic Web extends the network of hyperlinked human-readable web pages by inserting machine-readable metadata about pages and how they are related to each other. This enables automated agents to access the Web more intelligently and perform more tasks on behalf of users.

Many of the technologies proposed by the W3C already existed before they were positioned under the W3C umbrella. These are used in various contexts, particularly those dealing with information that encompasses a limited and defined domain, and where sharing data is a common necessity, such as scientific research or data exchange among businesses. In addition, other technologies with similar goals have emerged, such as microformats.

Limitations of HTML

Many files on a typical computer can be loosely divided into either human-readable documents, or machine-readable data. Examples of human-readable document files are mail messages, reports, and brochures. Examples of machine-readable data files are calendars, address books, playlists, and spreadsheets, which are presented to a user using an application program that lets the files be viewed, searched, and combined.

Currently, the World Wide Web is based mainly on documents written in Hypertext Markup Language (HTML), a markup convention that is used for coding a body of text interspersed with multimedia objects such as images and interactive forms. Metadata tags provide a method by which computers can categorize the content of web pages. In the examples below, the field names "keywords", "description" and "author" are assigned values such as "computing", and "cheap widgets for sale" and "John Doe".

<span id="mwASQ"></span><span class="p" id="mwASU"><</span><span class="nt" id="mwASY">meta</span> <span class="na" id="mwASc">name</span><span class="o" id="mwASg">=</span><span class="s" id="mwASk">"keywords"</span> <span class="na" id="mwASo">content</span><span class="o" id="mwASs">=</span><span class="s" id="mwASw">"computing, computer studies, computer"</span> <span class="p" id="mwAS0">/></span> <span class="p" id="mwAS4"><</span><span class="nt" id="mwAS8">meta</span> <span class="na" id="mwATA">name</span><span class="o" id="mwATE">=</span><span class="s" id="mwATI">"description"</span> <span class="na" id="mwATM">content</span><span class="o" id="mwATQ">=</span><span class="s" id="mwATU">"Cheap widgets for sale"</span> <span class="p" id="mwATY">/></span> <span class="p" id="mwATc"><</span><span class="nt" id="mwATg">meta</span> <span class="na" id="mwATk">name</span><span class="o" id="mwATo">=</span><span class="s" id="mwATs">"author"</span> <span class="na" id="mwATw">content</span><span class="o" id="mwAT0">=</span><span class="s" id="mwAT4">"John Doe"</span> <span class="p" id="mwAT8">/></span>

Because of this metadata tagging and categorization, other computer systems that want to access and share this data can easily identify the relevant values.

With HTML and a tool to render it (perhaps web browser software, perhaps another user agent), one can create and present a page that lists items for sale. The HTML of this catalog page can make simple, document-level assertions such as "this document's title is 'Widget Superstore'", but there is no capability within the HTML itself to assert unambiguously that, for example, item number X586172 is an Acme Gizmo with a retail price of €199, or that it is a consumer product. Rather, HTML can only say that the span of text "X586172" is something that should be positioned near "Acme Gizmo" and "€199", etc. There is no way to say "this is a catalog" or even to establish that "Acme Gizmo" is a kind of title or that "€199" is a price. There is also no way to express that these pieces of information are bound together in describing a discrete item, distinct from other items perhaps listed on the page.

Semantic HTML refers to the traditional HTML practice of markup following intention, rather than specifying layout details directly. For example, the use of <em> denoting "emphasis" rather than <i>, which specifies italics. Layout details are left up to the browser, in combination with Cascading Style Sheets. But this practice falls short of specifying the semantics of objects such as items for sale or prices.

Microformats extend HTML syntax to create machine-readable semantic markup about objects including people, organizations, events and products. Similar initiatives include RDFa, Microdata and Schema.org.

Semantic Web solutions

The Semantic Web takes the solution further. It involves publishing in languages specifically designed for data: Resource Description Framework (RDF), Web Ontology Language (OWL), and Extensible Markup Language (XML). HTML describes documents and the links between them. RDF, OWL, and XML, by contrast, can describe arbitrary things such as people, meetings, or airplane parts.

These technologies are combined in order to provide descriptions that supplement or replace the content of Web documents. Thus, content may manifest itself as descriptive data stored in Web-accessible databases, or as markup within documents (particularly, in Extensible HTML (XHTML) interspersed with XML, or, more often, purely in XML, with layout or rendering cues stored separately). The machine-readable descriptions enable content managers to add meaning to the content, i.e., to describe the structure of the knowledge we have about that content. In this way, a machine can process knowledge itself, instead of text, using processes similar to human deductive reasoning and inference, thereby obtaining more meaningful results and helping computers to perform automated information gathering and research.

An example of a tag that would be used in a non-semantic web page:

<span id="mwAWU"></span><span class="nt" id="mwAWY"><item></span>blog<span class="nt" id="mwAWc"></item></span>

Encoding similar information in a semantic web page might look like this:

<span id="mwAWs"></span><span class="nt" id="mwAWw"><item</span><span class="w" id="mwAW0"> </span><span class="na" id="mwAW4">rdf:about=</span><span class="s" id="mwAW8">"https://example.org/semantic-web/"</span><span class="nt" id="mwAXA">></span>Semantic<span class="w" id="mwAXE"> </span>Web<span class="nt" id="mwAXI"></item></span>

Tim Berners-Lee calls the resulting network of Linked Data the Giant Global Graph, in contrast to the HTML-based World Wide Web. Berners-Lee posits that if the past was document sharing, the future is data sharing. His answer to the question of "how" provides three points of instruction. One, a URL should point to the data. Two, anyone accessing the URL should get data back. Three, relationships in the data should point to additional URLs with data.

Tags and identifiers

Tags, including hierarchical categories and tags that are collaboratively added and maintained (e.g. with folksonomies) can be considered part of, of potential use to or a step towards the semantic Web vision.

Unique identifiers, including hierarchical categories and collaboratively added ones, analysis tools and metadata, including tags, can be used to create forms of semantic webs – webs that are to a certain degree semantic. In particular, such has been used for structuring scientific research i.a. by research topics and scientific fields by the projects OpenAlex, Wikidata and Scholia which are under development and provide APIs, Web-pages, feeds and graphs for various semantic queries.

Web 3.0

Tim Berners-Lee has described the Semantic Web as a component of Web 3.0.

People keep asking what Web 3.0 is. I think maybe when you've got an overlay of scalable vector graphics – everything rippling and folding and looking misty – on Web 2.0 and access to a semantic Web integrated across a huge space of data, you'll have access to an unbelievable data resource …

— Tim Berners-Lee, 2006

"Semantic Web" is sometimes used as a synonym for "Web 3.0", though the definition of each term varies.

Beyond Web 3.0

The next generation of the Web is often termed Web 4.0, but its definition is not clear. According to some sources, it is a Web that involves artificial intelligence, the internet of things, pervasive computing, ubiquitous computing and the Web of Things among other concepts. According to the European Union, Web 4.0 is "the expected fourth generation of the World Wide Web. Using advanced artificial and ambient intelligence, the internet of things, trusted blockchain transactions, virtual worlds and XR capabilities, digital and real objects and environments are fully integrated and communicate with each other, enabling truly intuitive, immersive experiences, seamlessly blending the physical and digital worlds".

Challenges

Some of the challenges for the Semantic Web include vastness, vagueness, uncertainty, inconsistency, and deceit. Automated reasoning systems will have to deal with all of these issues in order to deliver on the promise of the Semantic Web.

Vastness: The World Wide Web contains many billions of pages. The SNOMED CT medical terminology ontology alone contains 370,000 class names, and existing technology has not yet been able to eliminate all semantically duplicated terms. Any automated reasoning system will have to deal with truly huge inputs.
Vagueness: These are imprecise concepts like "young" or "tall". This arises from the vagueness of user queries, of concepts represented by content providers, of matching query terms to provider terms and of trying to combine different knowledge bases with overlapping but subtly different concepts. Fuzzy logic is the most common technique for dealing with vagueness.
Uncertainty: These are precise concepts with uncertain values. For example, a patient might present a set of symptoms that correspond to a number of different distinct diagnoses each with a different probability. Probabilistic reasoning techniques are generally employed to address uncertainty.
Inconsistency: These are logical contradictions that will inevitably arise during the development of large ontologies, and when ontologies from separate sources are combined. Deductive reasoning fails catastrophically when faced with inconsistency, because "anything follows from a contradiction". Defeasible reasoning and paraconsistent reasoning are two techniques that can be employed to deal with inconsistency.
Deceit: This is when the producer of the information is intentionally misleading the consumer of the information. Cryptography techniques are currently utilized to alleviate this threat. By providing a means to determine the information's integrity, including that which relates to the identity of the entity that produced or published the information, however credibility issues still have to be addressed in cases of potential deceit.

This list of challenges is illustrative rather than exhaustive, and it focuses on the challenges to the "unifying logic" and "proof" layers of the Semantic Web. The World Wide Web Consortium (W3C) Incubator Group for Uncertainty Reasoning for the World Wide Web (URW3-XG) final report lumps these problems together under the single heading of "uncertainty". Many of the techniques mentioned here will require extensions to the Web Ontology Language (OWL) for example to annotate conditional probabilities. This is an area of active research.

Standards

Standardization for Semantic Web in the context of Web 3.0 is under the care of W3C.

Components

The term "Semantic Web" is often used more specifically to refer to the formats and technologies that enable it. The collection, structuring and recovery of linked data are enabled by technologies that provide a formal description of concepts, terms, and relationships within a given knowledge domain. These technologies are specified as W3C standards and include:

Resource Description Framework (RDF), a general method for describing information
RDF Schema (RDFS)
Simple Knowledge Organization System (SKOS)
SPARQL, an RDF query language
Notation3 (N3), designed with human readability in mind
N-Triples, a format for storing and transmitting data
Turtle (Terse RDF Triple Language)
Web Ontology Language (OWL), a family of knowledge representation languages
Rule Interchange Format (RIF), a framework of web rule language dialects supporting rule interchange on the Web
JavaScript Object Notation for Linked Data (JSON-LD), a JSON-based method to describe data
ActivityPub, a generic way for client and server to communicate with each other. This is used by the popular decentralized social network Mastodon.

The Semantic Web Stack illustrates the architecture of the Semantic Web. The functions and relationships of the components can be summarized as follows:

XML provides an elemental syntax for content structure within documents, yet associates no semantics with the meaning of the content contained within. XML is not at present a necessary component of Semantic Web technologies in most cases, as alternative syntaxes exist, such as Turtle. Turtle is a de facto standard, but has not been through a formal standardization process.
XML Schema is a language for providing and restricting the structure and content of elements contained within XML documents.
RDF is a simple language for expressing data models, which refer to objects ("web resources") and their relationships. An RDF-based model can be represented in a variety of syntaxes, e.g., RDF/XML, N3, Turtle, and RDFa. RDF is a fundamental standard of the Semantic Web.
RDF Schema extends RDF and is a vocabulary for describing properties and classes of RDF-based resources, with semantics for generalized-hierarchies of such properties and classes.
OWL adds more vocabulary for describing properties and classes: among others, relations between classes (e.g. disjointness), cardinality (e.g. "exactly one"), equality, richer typing of properties, characteristics of properties (e.g. symmetry), and enumerated classes.
SPARQL is a protocol and query language for semantic web data sources.
RIF is the W3C Rule Interchange Format. It is an XML language for expressing Web rules that computers can execute. RIF provides multiple versions, called dialects. It includes a RIF Basic Logic Dialect (RIF-BLD) and RIF Production Rules Dialect (RIF PRD).

Current state of standardization

Well-established standards:

RDF - Resource Description Framework
RDFS - Resource Description Framework Schema
RIF - Rule Interchange Format
SPARQL - 'SPARQL Protocol and RDF Query Language'
Unicode
URI - Uniform Resource Identifier
OWL - Web Ontology Language
XML - Extensible Markup Language

Not yet fully realized:

Unifying Logic and Proof layers
SWRL - Semantic Web Rule Language

Applications

The intent is to enhance the usability and usefulness of the Web and its interconnected resources by creating semantic web services, such as:

Servers that expose existing data systems using the RDF and SPARQL standards. Many converters to RDF exist from different applications. Relational databases are an important source. The semantic web server attaches to the existing system without affecting its operation.
Documents "marked up" with semantic information (an extension of the HTML <meta> tags used in today's Web pages to supply information for Web search engines using web crawlers). This could be machine-understandable information about the human-understandable content of the document (such as the creator, title, description, etc.) or it could be purely metadata representing a set of facts (such as resources and services elsewhere on the site). Note that anything that can be identified with a Uniform Resource Identifier (URI) can be described, so the semantic web can reason about animals, people, places, ideas, etc. There are four semantic annotation formats that can be used in HTML documents; Microformat, RDFa, Microdata and JSON-LD. Semantic markup is often generated automatically, rather than manually.

Common metadata vocabularies (ontologies) and maps between vocabularies that allow document creators to know how to mark up their documents so that agents can use the information in the supplied metadata (so that Author in the sense of 'the Author of the page' will not be confused with Author in the sense of a book that is the subject of a book review).
Automated agents to perform tasks for users of the semantic web using this data.
Semantic translation. An alternative or complementary approach are improvements to contextual and semantic understanding of texts – these could be aided via Semantic Web methods so that only increasingly small numbers of mistranslations need to be corrected in manual or semi-automated post-editing.
Web-based services (often with agents of their own) to supply information specifically to agents, for example, a Trust service that an agent could ask if some online store has a history of poor service or spamming.
Semantic Web ideas are implemented in collaborative structured argument mapping sites where their relations are organized semantically, arguments can be mirrored (linked) to multiple places, reused (copied), rated, and changed as semantic distinct units. Ideas for such, or a more widely adopted "World Wide Argument Web", go back to at least 2007 and have been implemented to some degree in Argüman and Kialo. Further steps towards semantic web services may include enabling "Querying", argument search engines, and "summarizing the contentious and agreed-upon points of a discussion".

Such services could be useful to public search engines, or could be used for knowledge management within an organization. Business applications include:

Facilitating the integration of information from mixed sources
Dissolving ambiguities in corporate terminology
Improving information retrieval thereby reducing information overload and increasing the refinement and precision of the data retrieved
Identifying relevant information with respect to a given domain
Providing decision making support

In a corporation, there is a closed group of users and the management is able to enforce company guidelines like the adoption of specific ontologies and use of semantic annotation. Compared to the public Semantic Web there are lesser requirements on scalability and the information circulating within a company can be more trusted in general; privacy is less of an issue outside of handling of customer data.

Skeptical reactions

Practical feasibility

Critics question the basic feasibility of a complete or even partial fulfillment of the Semantic Web, pointing out both difficulties in setting it up and a lack of general-purpose usefulness that prevents the required effort from being invested. In a 2003 paper, Marshall and Shipman point out the cognitive overhead inherent in formalizing knowledge, compared to the authoring of traditional web hypertext:

While learning the basics of HTML is relatively straightforward, learning a knowledge representation language or tool requires the author to learn about the representation's methods of abstraction and their effect on reasoning. For example, understanding the class-instance relationship, or the superclass-subclass relationship, is more than understanding that one concept is a "type of" another concept. [...] These abstractions are taught to computer scientists generally and knowledge engineers specifically but do not match the similar natural language meaning of being a "type of" something. Effective use of such a formal representation requires the author to become a skilled knowledge engineer in addition to any other skills required by the domain. [...] Once one has learned a formal representation language, it is still often much more effort to express ideas in that representation than in a less formal representation [...]. Indeed, this is a form of programming based on the declaration of semantic data and requires an understanding of how reasoning algorithms will interpret the authored structures.

According to Marshall and Shipman, the tacit and changing nature of much knowledge adds to the knowledge engineering problem, and limits the Semantic Web's applicability to specific domains. A further issue that they point out are domain- or organization-specific ways to express knowledge, which must be solved through community agreement rather than only technical means. As it turns out, specialized communities and organizations for intra-company projects have tended to adopt semantic web technologies greater than peripheral and less-specialized communities. The practical constraints toward adoption have appeared less challenging where domain and scope is more limited than that of the general public and the World-Wide Web.

Finally, Marshall and Shipman see pragmatic problems in the idea of (Knowledge Navigator-style) intelligent agents working in the largely manually curated Semantic Web:

In situations in which user needs are known and distributed information resources are well described, this approach can be highly effective; in situations that are not foreseen and that bring together an unanticipated array of information resources, the Google approach is more robust. Furthermore, the Semantic Web relies on inference chains that are more brittle; a missing element of the chain results in a failure to perform the desired action, while the human can supply missing pieces in a more Google-like approach. [...] cost-benefit tradeoffs can work in favor of specially-created Semantic Web metadata directed at weaving together sensible well-structured domain-specific information resources; close attention to user/customer needs will drive these federations if they are to be successful.

Cory Doctorow's critique ("metacrap") is from the perspective of human behavior and personal preferences. For example, people may include spurious metadata into Web pages in an attempt to mislead Semantic Web engines that naively assume the metadata's veracity. This phenomenon was well known with metatags that fooled the Altavista ranking algorithm into elevating the ranking of certain Web pages: the Google indexing engine specifically looks for such attempts at manipulation. Peter Gärdenfors and Timo Honkela point out that logic-based semantic web technologies cover only a fraction of the relevant phenomena related to semantics.

Censorship and privacy

Enthusiasm about the semantic web could be tempered by concerns regarding censorship and privacy. For instance, text-analyzing techniques can now be easily bypassed by using other words, metaphors for instance, or by using images in place of words. An advanced implementation of the semantic web would make it much easier for governments to control the viewing and creation of online information, as this information would be much easier for an automated content-blocking machine to understand. In addition, the issue has also been raised that, with the use of FOAF files and geolocation meta-data, there would be very little anonymity associated with the authorship of articles on things such as a personal blog. Some of these concerns were addressed in the "Policy Aware Web" project and is an active research and development topic.

Doubling output formats

Another criticism of the semantic web is that it would be much more time-consuming to create and publish content because there would need to be two formats for one piece of data: one for human viewing and one for machines. However, many web applications in development are addressing this issue by creating a machine-readable format upon the publishing of data or the request of a machine for such data. The development of microformats has been one reaction to this kind of criticism. Another argument in defense of the feasibility of semantic web is the likely falling price of human intelligence tasks in digital labor markets, such as Amazon's Mechanical Turk.

Specifications such as eRDF and RDFa allow arbitrary RDF data to be embedded in HTML pages. The GRDDL (Gleaning Resource Descriptions from Dialects of Language) mechanism allows existing material (including microformats) to be automatically interpreted as RDF, so publishers only need to use a single format, such as HTML.

Research activities on corporate applications

The first research group explicitly focusing on the Corporate Semantic Web was the ACACIA team at INRIA-Sophia-Antipolis, founded in 2002. Results of their work include the RDF(S) based Corese search engine, and the application of semantic web technology in the realm of distributed artificial intelligence for knowledge management (e.g. ontologies and multi-agent systems for corporate semantic Web) and E-learning.

Since 2008, the Corporate Semantic Web research group, located at the Free University of Berlin, focuses on building blocks: Corporate Semantic Search, Corporate Semantic Collaboration, and Corporate Ontology Engineering.

Ontology engineering research includes the question of how to involve non-expert users in creating ontologies and semantically annotated content and for extracting explicit knowledge from the interaction of users within enterprises.

Future of applications

Tim O'Reilly, who coined the term Web 2.0, proposed a long-term vision of the Semantic Web as a web of data, where sophisticated applications are navigating and manipulating it. The data web transforms the World Wide Web from a distributed file system into a distributed database.