* 仕様書 [REFS[ - [1] [CITE@en[RFC 6903 - Additional Link Relation Types]] ([TIME[2013-07-07 18:30:35 +09:00]] 版) ]REFS] * 意味 [3] [[文脈資源]]が[[対象IRI]]で示される[[資源]]の[[実現値]]であることを示します。 特に[[HTTPヘッダー]]で使った場合、[[本体]]の[RUBYB[意味的な型]@en[semantic type]]がその[[対象IRI]]であることを示します。 [SRC[>>1]] [4] [CODE(HTTP)@en[[[type]]]] が複数指定した場合は複数の型の実現値を表します。 [SRC[>>1]] * メモ [2] 意味的な型といいますが、具体的にそれが一体何なのかは明確にされていません。 [[RFC]] の例示から [CODE(XMLa)@en[[[rdf:type]]]] のようなものと推察されますが、 [[RDF]] 乃至それに類するデータモデルとの関係も何ら示されておらず、詳細は不明です。 処理モデルも応用例も説明されていないので、どのように利用できるのかまったく不明です。 これでは著者の自己満足くらいにしか使えません。 ほとんど欠陥仕様と言っても良いでしょう。 * 歴史 [5] [CITE@en[Linked Data Platform 1.0]] ( ([TIME[2014-03-05 18:42:42 +09:00]] 版)) [6] [CITE@en[Linked Data Platform 1.0]] ([TIME[2015-02-27 16:06:09 +09:00]] 版) [FIG(quote)[ [FIGCAPTION[ [7] [CITE@en[Linked Data Platform 1.0]] ([TIME[2015-02-27 16:12:35 +09:00]] 版) ]FIGCAPTION] > 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''']'''. ]FIG] [FIG(quote)[ [FIGCAPTION[ [8] [CITE@en[Linked Data Platform 1.0]] ([TIME[2015-02-27 16:13:51 +09:00]] 版) ]FIGCAPTION] > 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. ]FIG] [FIG(quote)[ [FIGCAPTION[ [9] [CITE@en[Linked Data Platform Paging 1.0]] ([TIME[2015-07-01 15:13:26 +09:00]] 版) ]FIGCAPTION] > 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. ]FIG] [FIG(quote)[ [FIGCAPTION[ [10] [CITE@en[Web Annotation Protocol]] ([TIME[2017-02-24 02:14:26 +09:00]]) ]FIGCAPTION] > 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. ]FIG] [FIG(quote)[ [FIGCAPTION[ [11] [CITE@en[Web Annotation Protocol]] ([TIME[2017-02-24 02:14:26 +09:00]]) ]FIGCAPTION] > 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. ]FIG] [FIG(quote)[ [FIGCAPTION[ [12] [CITE@en[OSLC Core Version 3.0. Part 5: Attachments]] ([TIME[2017-04-05 01:00:00 +09:00]]) ]FIGCAPTION] > 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. ]FIG]