仕様書

意味

[3] 文脈資源が対象IRIで示される資源の実現値であることを示します。 特にHTTPヘッダーで使った場合、本体の意味的な型semantic typeがその対象IRIであることを示します。 >>1

[4] type が複数指定した場合は複数の型の実現値を表します。 >>1

メモ

[2] 意味的な型といいますが、具体的にそれが一体何なのかは明確にされていません。 RFC の例示から rdf:type のようなものと推察されますが、 RDF 乃至それに類するデータモデルとの関係も何ら示されておらず、詳細は不明です。 処理モデルも応用例も説明されていないので、どのように利用できるのかまったく不明です。 これでは著者の自己満足くらいにしか使えません。 ほとんど欠陥仕様と言っても良いでしょう。

歴史

[5] Linked Data Platform 1.0 ( ( 版)) http://www.w3.org/TR/2014/WD-ldp-20140311/#h5_ldpr-gen-linktypehdr

[6] Linked Data Platform 1.0 ( 版) https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h-ldpr-gen-linktypehdr

[7] Linked Data Platform 1.0 ( 版) https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h-ldpnr-type

4.4.1.2 LDP servers exposing an LDP Non-RDF Source may advertise this by exposing a HTTP Link header with a target URI of http://www.w3.org/ns/ldp#NonRDFSource, and a link relation type of type (that is, rel="type") in responses to requests made to the LDP-NR's HTTP Request-URI [RFC5988].

[8] Linked Data Platform 1.0 ( 版) https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#h-ldpc-linktypehdr

5.2.1.4 LDP servers exposing LDPCs must advertise their LDP support by exposing a HTTP Link header with a target URI matching the type of container (see below) the server supports, and a link relation type of type (that is, rel="type") in all responses to requests made to the LDPC's HTTP Request-URI. LDP servers may provide additional HTTP Link: rel="type" headers.

[9] Linked Data Platform Paging 1.0 ( 版) https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html#ldpr-pagingGET-page-type-reqd

LDP Paging servers must provide an HTTP Link header whose target URI is http://www.w3.org/ns/ldp#Page, and whose link relation type is type [RFC5988] in responses to GET requests with any in-sequence page resource as the Request-URI. This is one mechanism by which clients know that the resource is one of a sequence of pages.

[10] Web Annotation Protocol () https://w3c.github.io/web-annotation/protocol/wd/#h-annotation-retrieval

The response from the Annotation Server must have a Link header entry where the target IRI is http://www.w3.org/ns/ldp#Resource and the rel parameter value is type. The Annotation type of http://www.w3.org/ns/oa#Annotation may also be added with the same rel type. This is to let client systems know that the retrieved representation is a Resource and an Annotation, even if the client cannot process the representation's format.

[11] Web Annotation Protocol () https://w3c.github.io/web-annotation/protocol/wd/#h-container-retrieval

It must advertise its type by including a link where the rel parameter value is type and the target IRI is the appropriate Container Type, such as http://www.w3.org/ns/ldp#BasicContainer for Basic Containers.

[12] OSLC Core Version 3.0. Part 5: Attachments () http://docs.oasis-open.org/oslc-core/oslc-core/v3.0/cs01/part5-attachments/oslc-core-v3.0-cs01-part5-attachments.html

5.4.6 Clients may specify an LDP-NR interaction model when POSTing RDF content to an oslc:AttachmentContainer by including an HTTP Link header where the target URI is http://www.w3.org/ns/ldp#NonRDFSource and the link relation is type.