science

HTTPRange-14

HTTPRange-14 is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand HTTPRange-14 rather than just read about it. In short: httpRange-14 is a long-running logical conundrum or design problem in the semantic web. The problem arises because when HTTP is extended from referring only to documents to talking about real-world things (planets, flowers, emotions, Platonic forms, etc) the domain of HTTP GET becomes undefined.

Key takeaways

HTTPRange-14 belongs to science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect HTTPRange-14 to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of HTTPRange-14 from memory before moving on to harder problems.

Reference excerpt

httpRange-14 is a long-running logical conundrum or design problem in the semantic web. The problem arises because when HTTP is extended from referring only to documents to talking about real-world things (planets, flowers, emotions, Platonic forms, etc) the domain of HTTP GET becomes undefined.

History The HTTP protocol was originally designed to transfer information objects, specifically Hypertext such as HTML. The GET request was issued by a client to retrieve data at a particular URL. Retrieving non-HTML information objects (images, Flash files, CSS files, streaming video, etc) was not a problem, since all of these could be streamed across the network using standard approaches developed by earlier protocols. The semantic web was invented, spearheaded by the W3C and Tim Berners-Lee, which used URLs to refer to real world things (planets, flowers, emotions, Platonic forms, etc) which could not be reduced to network streams. The question of what web servers should do when asked for one of these things arose.

Use of # URIs of real world things can be limited to 'hash URIs', that is URIs containing a fragment identifier. These URIs cannot be directly deferenced via HTTP so the protocol does not need to worry about the conflict. In this approach a URI not ending in a hash is understood to refer to a document, whereas the same URI with a '#' appended can refer to an abstract concept.

Use of HTTP Status Code 303 See Other The HTTP Status Code 303 See Other is to be interpreted as follows:

A 303 response to a GET request indicates that the origin server does not have a representation of the target resource that can be transferred by the server over HTTP. However, the Location field value refers to a resource that is descriptive of the target resource, such that making a retrieval request on that other resource might result in a representation that is useful to recipients without implying that it represents the original target resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might be a useful description are outside the scope of HTTP. By sending a 303 when asked for a non-information resource and redirecting to an information resource about the non-information resource, the server answers the requesters information need without having to supply the actual thing. This is recommended as good practice by the W3C August 2007 draft.

Resolution The W3C's Cool URIs for the Semantic Web document recommends using one or other of these two methods, depending on the requirements of the project.

Implications The impact of the issue (more correctly the impact of confusion around the issue) is greatest in semantic web communities whose models involve large numbers of abstract concepts which cannot be serialised, such as the FRBR community.

Further reading http://www.w3.org/2001/tag/group/track/issues/14 http://www.w3.org/wiki/HttpRange14Webography http://www.ibiblio.org/hhalpin/homepage/notes/uri.html

References

Worked examples

Example 1 — a first encounter with HTTPRange-14

Start with the simplest possible case. Write down what HTTPRange-14 claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to HTTPRange-14 before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about HTTPRange-14 ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of HTTPRange-14

In research: HTTPRange-14 appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses HTTPRange-14 in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: HTTPRange-14 is common in secondary-school and first-year university syllabi. It links to neighbouring topics Semantic Web, so understanding it makes those chapters shorter.
In everyday life: Look for HTTPRange-14 outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “HTTPRange-14” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study HTTPRange-14 in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what HTTPRange-14 means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain HTTPRange-14 out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is HTTPRange-14 in simple terms?

Why does HTTPRange-14 matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study HTTPRange-14?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on HTTPRange-14.