Content deleted Content added
Ohnoitsjamie (talk | contribs) m Reverted edits by 2400:C600:3461:B0A2:1:0:BE4:AAE3 (talk) to last version by Duckmather |
HeyElliott (talk | contribs) m WP:N'T |
||
Line 30:
===Using HTTP URIs to identify abstract resources===
[[URL]]s, particularly [[uniform resource identifier|HTTP URI]]s, are frequently used to identify abstract resources, such as classes, properties or other kind of concepts. Examples can be found in RDFS or OWL [[Ontology (computer science)|ontologies]]. Since such URIs are associated with the HTTP protocol, the question arose of which kind of representation, if any, should one get for such resources through this protocol, typically using a web browser, and if the syntax of the URI itself could help to differentiate "abstract" resources from "information" resources. The URI specifications such as RFC 3986 left to the protocol specification the task of defining actions performed on the resources and they
For example: <code><nowiki>http://www.example.org/catalogue/widgets.html</nowiki></code> would both identify and locate a web page (maybe providing some human-readable description of the widgets sold by Silly Widgets, Inc.) whereas <code><nowiki>http://www.example.org/ontology#Widget</nowiki></code> would identify the abstract concept or class "Widget" in this company ontology, and would not necessarily retrieve any physical resource through [[HTTP protocol]]. But it has been answered that such a distinction is impossible to enforce in practice, and famous standard vocabularies provide counter-examples widely used. For example, the [[Dublin Core]] concepts such as "title", "publisher", "creator" are identified by "slash" URIs like <code><nowiki>http://purl.org/dc/elements/1.1/title</nowiki></code>.
|