Information Technology Reference
In-Depth Information
http:EntityHeader
: An OWL Class. “Entity-header fields define meta-
information about the entity-body or, if no body is present, about the resource
identified by the request” (Fielding et al. 1999). Sometimes called in HTTP
“meta-information” (Fielding et al. 1999). Various fields of the entity header can
define status codes (
http:StatusCode
), encoding (
http:MediaType
),
language (
http:ContentLanguage
), creation (
http:CreationDate
),
date of modification (
http:ModificationDate
), and so on.
-
rdfs:subClassOf ir:InformationRealization
-
http:hasComponent min 1 http:EntityHeaderField
http:hasHeaderFieldValue
: An OWL Object Property. A relation be-
tween an entity header field and its field values. It is specialized by several prop-
erties, each representing an entity header field such as
http:hasStatusCode
and
http:hasContentType
.
-
rdfs:domain http:HeaderField
WebRepresentation
: An OWL Class. A sequence of octets, along with
representation metadata describing those octets, that constitutes a record of the
state of the resource at the time when the representation is generated (Berners-
Lee et al. 2005). Note that the term 'representation' is used for this class in IETF
RFC 3968, but has been changed to 'web representation' to separate it from the
more general notion of 'representation' in philosophy (Jacobs and Walsh 2004)
-
rdfs:subClassOf http:Entity
-
locatedOn min 1 WebServer
WebResource
: An OWL Class. “A network data object or service” (Fielding
et al. 1999). As such, this is a resource that is accessible via the Web (Hayes
and Halpin 2008). Therefore, a web resource must have at least one URI and be
realized by at least one web representation.
-
rdfs:subClassOf InformationResource
-
isIdentifiedBy min 1 URI
-
ir:isRealizedBy min 1 WebRepresentation
3.4.4
Media Types
One intriguing problem, central to the notion of Web representations and resources,
is the connection between media types and resources. Very little work has been
done in this area, likely due to the lack of use of content negotiation in general
on the hypertext Web. For example, instead of using content negotiation to return
versions of the same resource in multiple languages, many sites use explicit links.
The only substantial work so far on this issue has been Berners-Lee's note
Generic
Search WWH ::
Custom Search