> [!tldr] [[HTML]] with [[Ontology]]s The semantic web is where [[URI]]s and the [[Resource Description Framework]] meet at great scale. > [!quote] From the source > The Semantic Web is envisioned as a decentralised world-wide information space for sharing machine-readable data with a minimum of integration costs. Its two core challenges are the distributed modelling of the world with a shared data model, and the infrastructure where data and schemas can be published, found and used. > ... > A basic question is thus how to publish information about resources in a way that allows interested users and software applications to find and interpret them. > ... > On the Semantic Web, ==all information has to be expressed as _statements_ about _resources_==, like _the members of the company Example.com are Alice and Bob_ or _Bob's telephone number is "+1 555 262"_ or _this Web page was created by Alice_. A *resource* found at a [[URI]] is, in theory, static. However it may have many different *forms* that it can be represented in (e.g. [[PDF]], [[XML]], etc). [[XLMHttpRequest vs Fetch|HTTP Requests]] can specify parameters for the response to the URI fetch - this is called [[Content Negotiation]]. ![[Pasted image 20260824222247.png]] It's important to distinguish between whether a [[URI]] is pulling up *the thing* or instead something *describing the thing*. ## Stack The Semantic Web is composed of a stack of technologies including: - [[Resource Description Framework|RDF]] - [[SPARQL]] - [[JSON-LD]] - [[OWL]] - [[SKOS]] - [[SHACL]] And some others. ## Rules > [!quote] From the source > > 1. Be on the Web. > > Given only a URI, machines and people should be able to retrieve a description about the resource identified by the URI from the Web. Such a look-up mechanism is important to establish shared understanding of what a URI identifies. Machines should get RDF data and humans should get a readable representation, such as HTML. The standard Web transfer protocol, HTTP, should be used. > > 2. Be unambiguous. > > There should be no confusion between identifiers for Web documents and identifiers for other resources. URIs are meant to identify only one of them, so one URI can't stand for both a Web document and a real-world object. **** # More ## Source - https://www.w3.org/TR/cooluris/