如果使用 URI 进行配置文件标识，则它 SHOULD 是一个 HTTP URI，
解引用后可得到该配置文件的描述。
也 MAY 使用其他种类的 URI，例如 URN，而这些 URI 可能不可
解引用。
如果使用令牌，则它 MUST 在一对
请求/响应消息中明确标识该
数据配置文件。
服务器 MUST 声明该令牌可以映射到某个
URI 的上下文。
# A request for all the profiles to which representations of resource a conform
GET /resource/a?_profile=alt HTTP/1.1
---
# The server returns a list of profiles both in its HTTP response header and also
# in the response body (HTML). Note that the action of returning the response message
# conforms to the QSA Functional Profile and this is indicated with the Link header
# combined with the "profile" relation
HTTP/1.1 200 OK
Content-Type: text/html
Link: <http://www.w3.org/ns/dx/connegp/profile/qsa>; rel="profile"
# This Link header indicates representations are available that conform to Profile X
# & Y and that the Profile X-conformant representations are available in HTML
# & XML Media Types.
Link:
<http://example.org/resource/a?_profile=profile-x&_mediatype=text/html>;
rel="canonical"; type="text/html";
formats="http://otherexample.org/profile/x",
<http://example.org/resource/a?_profile=profile-x&_mediatype=application/xml>;
rel="alternate";
type="application/xml";
formats="http://otherexample.org/profile/x",
<http://example.org/resource/a?_profile=profile-y&_mediatype=application/xml>;
rel="alternate";
type="application/xml";
formats="http://otherexample.org/profile/y"
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Profiles for Resource A</title>
</head>
<body>
<h1>Profiles available for Resource X</h1>
<ul>
<li><a href="?_profile=profile-x&_mediatype=text/html">X, in HTML</a></li>
<li><a href="?_profile=profile-x&_mediatype=application/xml">X, in XML</a></li>
<li><a href="?_profile=profile-y&_mediatype=application/xml">Y, in XML</a></li>
</ul>
</body>
</html>
# A request for resource a according to Profile x is made
GET /resource/a HTTP/1.1
Accept-Profile: <http://example.org/profile/x>
---
# The server returns a representation of Resource a conforming with Profile x
HTTP/1.1 200 OK
Link: <http://example.org/profile/x>; rel="profile"
[response body]
# A request for a non-information resource a according to Profile x is made
GET /resource/a HTTP/1.1
Accept-Profile: <http://example.org/profile/x>
---
# The server returns a 303 Redirect to another URI identifying an information
# resource that then returns the requested resource representation. The redirecting
# server indicates the profile to which the redirected to resource representation
# conforms
HTTP/1.1 303 See Other
Location: http://example.org/info-resource/b
Link: <http://example.org/profile/x>; rel="profile"
---
# The client now requests the indicated information resource. Note that the
# Accept-Profile header is no longer needed since the original response has
# catered for that in the redirect response
GET /info-resource/b HTTP/1.1
---
# The final server response with the information resource. Note that this
# response does not include the profile-indicating Link rel="profile" header
HTTP/1.1 200 OK
[response body]
# A request for Resource A whose representation conforms
# to Profile X is made
GET /resource/a HTTP/1.1
Accept-Profile: <http://example.org/profile/x>
[more request headers]
---
# The server is able to respond with a representation of
# Resource a according to Profile Y which it knows is a
# profile of Profile X
# The server responds with the list of profiles that it knows
# the resource representations conforms to ensuring that the
# requested profile, Profile X, is listed. Here Profile Y and
# a further profile irrelevant for the client, Profile Z, are
# indicated.
HTTP/1.1 200 OK
[other response headers]
Link: <http://example.org/profile/x>; rel="profile", \
<http://example.org/profile/y>; rel="profile", \
<http://example.org/profile/z>; rel="profile"
[more response headers]
[content conforming to to Profile X, Y & Z]
当返回的资源符合两个或更多不属于同一配置文件层次结构的配置文件时
（即该资源符合一组配置文件，但其中一些彼此独立，并非该集合中其他配置文件的
特化
配置文件），服务器 SHOULD 指示其符合每个独立配置文件。
POST 和 PUT 方法被认为不在此功能配置文件的范围内。目前尚不清楚
这些 HTTP 方法会实现所提议抽象模型中的哪些功能。
可以在 POST 和 PUT
请求中指定带有 rel="profile" 的 Link 标头，以传达
请求消息内容的一致性。
尽管服务器可以自由地按其认为合适的方式实现协商，
但如果用户代理发送了 Accept-Profile 标头，
它们 SHOULD 将不符合任何所列配置文件的表示
视为客户端不可解释。
这意味着，一个符合所列配置文件的表示，
即使在其他维度上的偏好分数较低，
也 SHOULD 被认为比
一个在其他维度上偏好分数更高、
但不符合任何所列配置文件的表示更受期望。
如果未给出 Accept-Profile 标头偏好，
则在协商目的下 SHOULD 忽略 profile 维度。
不过，在所有情况下，
服务器响应 SHOULD 包含一个
带有 rel="profile" 的 Link 标头，
列出它所知该表示符合的所有配置文件的 URI。
8.2.1 列出配置文件
检索服务器针对特定资源所支持配置文件列表的首选方式，
是对该资源发出 GET 或 HEAD 请求。
在任一情况下，实现
基于配置文件的内容协商的服务器 SHOULD 返回一个 HTTP
Link 标头，其中包含关于该
资源的默认表示和任何备用表示的信息，
包括它们所符合的配置文件。默认表示——即在未请求特定表示时
将返回的表示——
SHOULD 由 rel="canonical" 标识，其他表示
由
rel="alternate" 标识。
# The profile URI in the "anchor" element is linked to the token "igsn-r1"
# Further, the relation "type" is used to inform
# that the anchor resource is of type "dcterms:Standard"
Link: <http://www.w3.org/ns/dx/prof/Profile>;
rel="type";
token="igsn-r1";
anchor=<http://schema.igsn.org/description/1.0>
服务器 MAY 在 token/URI 映射旁边向 Link 标头添加更多属性，
例如备用表示数据模型内容。
示例 12 展示了带有多个属性的
Link 标头中的令牌。
# The Profile with URI urn:example:profile:marc21-dnb is mapped to the token "dnb"
# and the Profile with URI http://example.org/profiles/marc21-loc is mapped to the token "loc"
HEAD /resource/a HTTP/1.1
Accept: text/turtle
[more request headers]
---
HTTP/1.1 200 OK
Content-Type: text/turtle
Content-Location: http://example.org/resource/a.profx.ttl
Link: <urn:example:profile:x>; rel="profile"
Link:
<http://www.w3.org/ns/dx/prof/Profile>; rel="type"; token="dnb"; anchor=<urn:example:profile:marc21-dnb>,
<http://www.w3.org/ns/dx/prof/Profile>; rel="type"; token="loc"; anchor=<http://example.org/profiles/marc21-loc>,
<http://example.org/resource/a.profdnb.ttl>; rel="canonical"; type="text/turtle"; formats="urn:example:profile:marc21-dnb",
<http://example.org/resource/a.profloc.ttl>; rel="alternate"; type="text/turtle"; formats="http://example.org/profiles/marc21-loc",
<http://example.org/resource/a.profdnb.xml>; rel="alternate"; type="application/xml"; formats="urn:example:profile:marc21-dnb",
<http://example.org/resource/a.profloc.xml>; rel="alternate"; type="application/xml"; formats="http://example.org/profiles/marc21-loc",
<http://example.org/resource/a.html>; rel="alternate"; type="text/html"
[more response headers]
8.2.2 按配置文件获取资源
获取符合特定配置文件的资源表示，是通过针对该资源发出
HTTP GET 请求，并在 Accept-Profile 标头中指定
所需的配置文件 URI 来完成的。
实现基于配置文件内容协商的服务器 MUST 使用包含
一个 Link 标头的 HTTP 响应标头作出响应，
该标头带有 rel="profile"，指示返回的配置文件。
请求和响应中的 URI 均 MUST 用尖括号
“<”和“>”括起来。
可以提供一组可接受的配置文件 URI；如果提供，则它们
MUST 由逗号分隔，
或者位于单独的 Accept-Profile 标头中。
客户端 MAY 使用质量指示符
（q 值）作为排序机制来指示偏好，该指示符
与 URI 之间用分号“;”分隔。带 q 值的 URI（本例中为 URN）的示例是
<urn:example:profile:x>;q=1.0,，其中 URI
为 <urn:example:profile:x>，q 值为 q=1.0。
GET /resource/a?_profile=alt&_mediatype=application/json HTTP/1.1
---
# The response shows that representations of the resource can be delivered according
# to two profiles identified by the tokens profile-x & profile-y
# and that profile-x-conformant representations are available in XML & JSON
# where as profile-y-conformant representations are only available in XML
# The content in the JSON body of the response is equivalent to that of the Link header
# and can easily be mapped to the Alternate Representations Data Model, just as the Link
# information is in Figure 3.
# Both the Link header and the JSON body include profile URI/token mappings
HTTP/1.1 200 OK
Content-Type: application/json
Link: <http://www.w3.org/ns/dx/connegp/profile/qsa>; rel="profile",
<http://example.org/resource/a?_profile=profile-x&_mediatype=application/json>;
rel="canonical";
type="application/json";
formats="http://otherexample.org/profile/x",
<http://example.org/resource/a?_profile=profile-x&_mediatype=application/xml>;
rel="alternate";
type="application/xml";
formats="http://otherexample.org/profile/x",
<http://example.org/resource/a?_profile=profile-y&_mediatype=application/xml>;
rel="alternate";
type="application/xml";
formats="http://otherexample.org/profile/y"
{
"resource": "http://example.org/resource/a",
"profiles": [
{
"token": "profile-x",
"uri": "http://otherexample.org/profile/x",
"media_types": ["application/json", "application/xml"]
},
{
"token": "profile-y",
"uri": "http://otherexample.org/profile/y",
"media_types": ["application/xml"]
}
]
}
8.3.2.1 QSA 备用
表示数据模型实现
按照 QSA 功能配置文件实现本规范的实现
MUST
按照备用表示数据模型传达其
备用表示信息。它们 MAY 按照 HTTP 标头功能配置文件使用
HTTP Link 标头来实现，也 MAY 使用其他方式。
如 [RFC8288]（Web Linking）引言中所述，HTML 和
一些其他数据模型具有
“定义良好的链接概念”，因此 QSA
实现者 MAY 通过 HTTP 正文内容来实现备用
表示数据模型信息的传达，可能采用 HTML 或其他数据
模型/格式。这可以帮助使用 QSA 实现的人类
客户端
用户，使其可在 Web 浏览器中或在可下载文件中看到这些信息。
示例 10 中
Link 标头信息的一种可能 HTML 表达，见下方
示例 17。注意，上方的
示例 16
给出了根据备用
表示数据模型对 Link 标头信息进行 JSON 格式表达的一种可能形式。
按照 7.2 配置文件
标识，所有配置文件 MUST 由 URI 标识，因为
URI 具有全局唯一性，
因此不需要注册即可避免标识符重复。然而，符合本规范任一
QSA 功能配置文件的系统，
在客户端/服务器交互期间可以不使用 URI 来标识配置文件，
而是 MAY 使用未注册且非全局唯一的令牌来标识
配置文件；但如果这样做，它们 MUST 提供一种方式，
让客户端发现配置文件 token/URI 映射。
希望向客户端提供配置文件 URI 令牌的
QSA 服务器 SHOULD
遵循
8.2.1.2 令牌映射中为 HTTP
标头功能配置文件提供的说明。
8.3.2.3 资源 URL
正在进行基于 QSA 的配置文件协商的资源 URL
SHOULD NOT 本身成为任何基于
QSA 的系统中其他资源 URI 的
QSA 值。这类机制可以在内部使用，且遗留系统也用于
配置文件协商，但最好对
客户端隐藏，
以使这些 QSA 配置文件的一致性更容易识别。
示例 18展示了这一点。
For the representation of Resource X, according to Profile Y, in Media Type Z:
Rather than:
GET /single/endpoint \
?resource=http://example.org/resource/X \
&_profile=Y \
&_mediatype=Z HTTP/1.1
Use:
GET /resource/X?_profile=Y&_mediatype=Z HTTP/1.1
8.3.3 按配置文件获取资源
为符合本规范的“QSA 功能配置文件”
配置文件，
服务器MUST 允许
客户端根据其用 _profile 查询
字符串标识的配置文件请求资源。
由于可以使用
令牌或 URI
来标识配置文件，服务器
MUST 接受任一种。服务器 MAY
接受编码和未编码的 URI，但 MAY 也可以只接受其中一种。
URI MUST 用
尖括号“<”和“>”括起来。
# A client makes a request for Resource A not knowing if any Content
# Negotiation by Profile is supported. It supplies an Accept-Profile
# header just in case. For extra efficiency, the client could have
# made a HEAD request instead of a GET
GET /resource/a HTTP/1.1
Accept-Profile: <http://example.org/profile/x>
# The server does not understand the HTTP Get Resource By Profile
# request (doesn't support the HTTP Headers Functional Profile) but is
# able to supply an HTTP Link header indicating alternate resource
# representations. It can be seen from the Link header that keys other
# than _profile & _mediatype are in use - view & format - thus this is
# QSA Alt, not a QSA Functional Profile-conformant system
# The resource representations available conform to profile-x & profile-y.
# The profile-x-conformant representation is available in HTML & Turtle,
# the profile-y-conformant representation is available only in XML
HTTP/1.1 200 OK
Link:
<http://example.org/resource/a?view=profile-x&format=text/html>;
rel="canonical";
type="text/html";
formats="http://otherexample.org/profile/x",
<http://example.org/resource/a?view=profile-x&format=text/turtle>;
rel="alternate";
type="text/turtle";
formats="http://otherexample.org/profile/x",
<http://example.org/resource/a?view=profile-y&format=application/xml>;
rel="alternate";
type="application/xml";
formats="http://otherexample.org/profile/y"
# Note that here the server does not directly indicate the profile served
# (there is no Link header with rel="profile" present) but this can be inferred
# by the link header with rel="canonical"
虽然上方 示例 19中的 Link 标头
传达了列出配置文件请求所传达的所有信息，
但它不能直接在 Web 浏览器中看到。示例 16 展示了一对
请求/响应，其中包含等价的 Link 标头和 HTTP 正文信息来列出
配置文件；后者可在浏览器中看到，但构造此请求的客户端
依赖于它知道
QSA 键/值对 _profile=alt
用于触发该响应，而不是
服务器的默认资源表示。
# The profile URI in the "anchor" element is linked to the token "igsn-r1"
# Further, the relation "type" is used to inform
# that the anchor resource is of type "dcterms:Standard"
Link: <http://www.w3.org/ns/dx/prof/Profile>;
rel="type";
token="igsn-r1";
anchor=<http://schema.igsn.org/description/1.0>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX prof: <http://www.w3.org/ns/dx/prof/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX cnpr: <http://www.w3.org/ns/dx/connegp/profile/>
<https://www.w3.org/TR/dx-connegp/> a dcterms:Standard ;
rdfs:label "Content Negotiation by Profile" ;
rdfs:comment "W3C Recommendation (a standard) for Content
Negotiation by Profile"@en .
cnpr:http a prof:Profile ;
prof:isProfileOf <https://www.w3.org/TR/dx-connegp/> ;
rdfs:label "HTTP Headers Functional Profile" ;
rdfs:comment "For conformance with the functional profile of Content Negotiation by
Profile presented in § 7.2 Hypertext Transfer Protocol Headers."@en ;
skos:scopeNote "To be used if a resource conforms to the HTTP Headers functional profile"@en .
cnpr:qsa a prof:Profile ;
prof:isProfileOf cnpr:qsa-alt ;
rdfs:label "QSA Functional Profile"@en ;
rdfs:comment "For conformance with the functional profile of Content Negotiation by
Profile presented in § 7.3 URL Query String Arguments."@en ;
skos:scopeNote "To be used if a resource conforms to the QSA
Functional Profile using
the Query String Arguments _profile and _mediatype as per the
recommendations in § 7.3 URL Query String Arguments."@en .
cnpr:qsa-alt a prof:Profile ;
prof:isProfileOf <https://www.w3.org/TR/dx-connegp/> ;
rdfs:label "QSA Alternate Keywords Functional Profile" ;
rdfs:comment "For conformance with the functional profile of Content Negotiation by
Profile presented in § 7.3 URL Query String Arguments."@en ;
skos:scopeNote "To be used if a resource conforms to the QSA
Functional Profile but
uses alternate keywords for the Query String Arguments _profile and
_mediatype, as allowed by the recommendations in § 7.3 URL Query
String Arguments."@en .
cnpr:rrd a prof:Profile ;
prof:isProfileOf <https://www.w3.org/TR/dx-connegp/> ;
rdfs:label "Resource Representation Description Profile"@en ;
rdfs:comment "For conformance with Content Negotiation by Profile § 6.3.2 get
resource by profile."@en ;
skos:scopeNote "To be used if a resource representation is able to indicate which
profile(s) it conforms to, in its appropriate functional profile,
as per the abstract specification in § 6.3.2 get resource by
profile."@en .
<http://example.com/service/xx>
a dcat:DataService ;
dcterms:title "Web Service XX" ;
dcterms:description "A dummy Web Service claiming conformance to a profile of the Content
Negotiation by Profile specification also annotated with other
DCAT-2 recommended properties."@en ;
# URI for the QSA Alternate Keywords Functional Profile
dcterms:conformsTo <http://www.w3.org/ns/dx/connegp/profile/qsa-alt> ;
# it's a public service
dcterms:accessRights <http://publications.europa.eu/resource/authority/access-right/PUBLIC>
# where the service actually is, online
dcat:endpointURL <http://example.com/service/v2/xx> ;
# a human- and machine-readable documentation endpoint for the service using the
# Swagger UI system
dcat:endpointDescription <http://example.com/service/v2/xx/swagger> ;
PREFIX altr: <http://www.w3.org/ns/dx/connegp/altr#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX sdo: <https://schema.org/>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
<http://www.w3.org/ns/dx/connegp/altr>
a owl:Ontology ;
rdfs:label "Alternative Profiles Ontology" ;
rdfs:comment """This ontology allows for the description of representations of Internet resources.
Representations may conform to prof:Profile instances and may have the format of a particular
dcterms:MediaType."""@en ;
dcterms:created "2019-08-07"^^xsd:date ;
dcterms:modified "2024-02-07"^^xsd:date ;
dcterms:creator [
a sdo:Person ;
sdo:affiliation <https://kurrawong.ai> ;
sdo:email <mailto:nick@kurrawong.ai> ;
sdo:identifier <http://orcid.org/0000-0002-8742-7730> ;
sdo:name "Nicholas J. Car" ;
] ;
.
<https://kurrawong.ai>
a sdo:Organization ;
sdo:name "KurrawongAI" ;
sdo:url "https://kurrawong.ai"^^xsd:anyURI ;
.
dcterms:conformsTo
a owl:ObjectProperty ;
rdfs:label "conforms to" ;
dcterms:source dcterms:conformsTo ;
skos:scopeNote "Use this property to indicate a dcterms:Standard that a altr:Representation conforms
to." ;
.
altr:hasRepresentation
a owl:ObjectProperty ;
rdfs:label "has representation" ;
skos:definition "Indicates a Representation of a Resource."@en ;
rdfs:domain rdfs:Resource ;
rdfs:range altr:Representation ;
skos:scopeNote "Use this property to indicate a the HTTP-delivered representation of a resource." ;
.
altr:hasDefaultRepresentation
a owl:ObjectProperty ;
rdfs:label "has default representation" ;
skos:definition "Indicates the default Representation of a Resource."@en ;
rdfs:domain altr:Representation ;
rdfs:subPropertyOf altr:hasRepresentation ;
skos:scopeNote "Use this property to indicate the default HTTP-delivered representation of a
resource that is obtained when no further instructions are given to a server to obtain a resource's
representation other than the identification (URI) of the resource" ;
.
rdfs:Resource
a owl:Class ;
rdfs:label "Resource" ;
skos:definition "The class resource, everything."@en ;
dcterms:source "http://www.w3.org/2000/01/rdf-schema#Resource" ;
skos:scopeNote "In the context of the Alternative Profiles Ontology, rdfs:Resource instances are
used to identify Internet resources, that is items identified by a URI." ;
.
altr:Representation
a owl:Class ;
rdfs:label "Representation" ;
skos:definition "An abstraction of the current or desired state of a thing in HTTP
communications."@en ;
dcterms:source <https://httpwg.org/specs/rfc7230.html> ;
rdfs:isDefinedBy <http://www.w3.org/ns/dx/connegp/altr> ;
skos:scopeNote "Use this class to indicate instances of representations of resources" ;
.
dcterms:Standard
a owl:Class ;
rdfs:label "Standard" ;
skos:definition "A basis for comparison; a reference point against which other things can be
evaluated."@en ;
dcterms:source "http://purl.org/dc/terms/Standard" ;
skos:scopeNote "In the context of the Alternative Profiles Ontology, use this class to indicate
instances of information models that representations of resources can conform to." ;
.
PREFIX ex: <http://example.org/>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
dcterms:format
a owl:ObjectProperty ;
rdfs:label "format" ;
skos:definition "The file format, physical medium, or dimensions of the resource."@en ;
dcterms:source dcterms:format ;
rdfs:range dcterms:MediaType ;
skos:scopeNote "Use this property to indicate an IANA Media Type of a resource's
representation " .
ex:defaultFormat
a owl:DataTypeProperty ;
rdfs:label "default format" ;
skos:definition "Indicates the default Representation of a Resource for the specified
Standard."@en ;
rdfs:domain
rdfs:range xsd:boolean ;
skos:scopeNote "Use this property to indicate which of more than one resource
representations that conforms to a profile is the default for get
resource by profile requests." .
dcterms:MediaType
a owl:Class ;
rdfs:label "Media Type" ;
skos:definition "A file format or physical medium."@en ;
dcterms:source "http://purl.org/dc/terms/MediaType" ;
skos:scopeNote "In the context of this mode, use this class to indicate
the IANA Media Type of a resource's representation." .
示例 22：
在 RDF（turtle）中实现 Alternative Profiles 数据模型的扩展实现，展示媒体
类型信息
PREFIX altr: <http://www.w3.org/ns/dx/connegp/altr#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
# This Resource A has 5 Representations, the 3rd of which is the default.
# Some of the Representations conform to the same Standard but are formatted
# according to different Media Types. Some Representations contain no Media
# Type information.
<http://example.org/resource/a>
a rdfs:Resource ;
rdfs:label "Resources A" ;
altr:hasRepresentation :rep-1 , :rep-2 , :rep-3 , :rep-4 , :rep-5 ;
altr:hasDefaultRepresentation :rep-3 .
:rep-1
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/x> ;
dcterms:format "application/xml" .
:rep-2
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/y> .
# This representation is the default for the set of representations
# that conform to <http://otherexample.org/profile/z>
:rep-3
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/z> .
dcterms:format "text/html" ;
ex:isProfilesDefault "true" .
:rep-4
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/z> ;
dcterms:format "text/turtle" .
:rep-5
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/z> ;
dcterms:format "application/ld+json" .
A.4.3 模型使用示例
示例 23 是一个按照 Alternative Profiles Data
Model 的 OWL 实现创建的 RDF 数据实例，随后
示例 24 以多种格式展示相同内容。
PREFIX altr: <http://www.w3.org/ns/dx/connegp/altr#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
# This Resource A has 3 Representations, the 3rd of which is the default
<http://example.org/resource/a>
a rdfs:Resource ;
rdfs:label "Resources A" ;
altr:hasRepresentation :rep-1 , :rep-2 , :rep-3 ;
altr:hasDefaultRepresentation :rep-3 .
# Each Representation and the Standard each conforms to, X, Y & Z
:rep-1
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/x> .
:rep-2
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/y> .
:rep-3
a altr:Representation ;
dcterms:conformsTo <http://otherexample.org/profile/z> .
# The content of the previous example expressed as in an HTTP Link header
# as per the HTTP Application Profile of this Specification with the
# default Representation indicated by the use of rel="canonical". Note the
# Representations are seen, one per Link result comma-separated, identified
# only by the combination of the Resource URI, the URI of the Standard to
# which they conform and the rel attribute - they do not have individual
# identifiers
Link:
<http://example.org/resource/a>;
rel="alternate";
formats="http://otherexample.org/profile/x",
<http://example.org/resource/a>;
rel="alternate";
formats="http://otherexample.org/profile/y",
<http://example.org/resource/a>;
rel="canonical";
formats="http://otherexample.org/profile/z"
---
# The content of the previous example expressed as in table form
# such as could potentially be expressed in the HTML body of an HTTP
# response. The Resource URIs include Query String Arguments that,
# when specified, allow the individual Representations to be returned,
# as per the QSA Application Profile below.
---------------------------------------------------------------------------------------
| Shortened Resource URI | URI of profile conformed to | Default |
---------------------------------------------------------------------------------------
| http://.../resource/a?_profile=prof-x | http://otherexample.org/profile/x | |
| http://.../resource/a?_profile=prof-y | http://otherexample.org/profile/y | |
| http://.../resource/a?_profile=prof-z | http://otherexample.org/profile/z | Yes |
---------------------------------------------------------------------------------------
PREFIX ex: <http://example.org#>
PREFIX dcat: <http://www.w3.org/ns/dcat#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX prof: <http://www.w3.org/ns/dx/prof/>
# A Dataset has a Distribution
:aDataset dcat:distribution :aDatasetDistribution .
# A data profile that the Distribution conforms to
ex:someDataProfile
a prof:Profile ;
# profile details
.
# A Distribution that can be accessed by a DataService that support Content
# Negotiation by Profile. The Distribution's content conforms to the Profile above
:aDatasetDistribution
a dcat:Distribution ;
dcterms:conformsTo ex:someDataProfile ;
dcat:accessService ex:connegDataAccessService .
# The Service used to access the Dataset's Distribution. The Service itself conforms
# to two functional profiles of Content Negotiation by Profile
ex:connegDataAccessService
a dcat:DataService ;
dcterms:conformsTo
<http://www.w3.org/ns/dx/connegp/profile/http> ,
<http://www.w3.org/ns/dx/connegp/profile/qsa> ;
# Declare that the Dataset may be invoked by URI, its id, using Content
# Negotiation by Profile
dcat:endPointURL :aDataset .
