From opengeospatial/ogc-feat-geo-json#129:
We will add "profile" as an additional link attribute as a hint indicating what the profile of the result of dereferencing the link should be. It should only be used in combination with the "type" attribute (since the value identifies the profile of a media type). The "profile" link attribute should be added to the OGC Link schema consistently. In Features Part 1 we will add it in the planned revision 1.1.
This also aligns Features with OGC API Records.
In Features this should be used in at least the following links:
self/alternate linksitems links from the collection
The "profile" link attribute is especially important in cases where different profiles of a format / media type are important to distinguish. The main cases in OGC standards at the moment are the GeoJSON profiles (rfc7946, jsonfg, and jsonfg-plus).
In general multiple profiles may apply (like in the profile query parameter, which is an array).
In a Link header, the profile URIs have to be concatenated, separated by whitespace (like in the link attribute "rel").
In a JSON Link object "profile" is an array, too. See Records.
Example in a collection:
{
"href": "/collections/foo/items?f=json&profile=rfc7946",
"type": "application/geo+json",
"profile": [ "http://www.opengis.net/def/profile/ogc/0/rfc7946" ],
"rel": "items",
"title": "The 'foo' features in GeoJSON"
},
{
"href": "/collections/foo/items?f=json&profile=jsonfg",
"type": "application/geo+json",
"profile": [ "http://www.opengis.net/def/profile/ogc/0/jsonfg" ],
"rel": "items",
"title": "The 'foo' features in JSON-FG"
}
From opengeospatial/ogc-feat-geo-json#129:
This also aligns Features with OGC API Records.
In Features this should be used in at least the following links:
self/alternatelinksitemslinks from the collectionThe "profile" link attribute is especially important in cases where different profiles of a format / media type are important to distinguish. The main cases in OGC standards at the moment are the GeoJSON profiles (
rfc7946,jsonfg, andjsonfg-plus).In general multiple profiles may apply (like in the
profilequery parameter, which is an array).In a
Linkheader, the profile URIs have to be concatenated, separated by whitespace (like in the link attribute "rel").In a JSON Link object "profile" is an array, too. See Records.
Example in a collection:
{ "href": "/collections/foo/items?f=json&profile=rfc7946", "type": "application/geo+json", "profile": [ "http://www.opengis.net/def/profile/ogc/0/rfc7946" ], "rel": "items", "title": "The 'foo' features in GeoJSON" }, { "href": "/collections/foo/items?f=json&profile=jsonfg", "type": "application/geo+json", "profile": [ "http://www.opengis.net/def/profile/ogc/0/jsonfg" ], "rel": "items", "title": "The 'foo' features in JSON-FG" }