There is no way to add attribution about the collections except through the description field

[ghobona]

The need to add a copyright statement, for example "Contains OS data © Crown Copyright and database right 2020", uncovered the need to add attribution about the collections and on the dataset landing page.

[cmheazel]

The JSON encodings allow you to add elements and still validate against the schema.
This information can also be included in the OpenAPI document.

[jerstlouis]

@cmheazel I think the key point here though is to have a standardized element (e.g. attribution) that clients can rely on, and that server know to populate.

[cmheazel]

@jerstlouis as always, if we can get agreement ---

[pomakis]

An "attribution" element at the {collectionId} endpoint (and possibly also at the data-set landing page endpoint) would be very useful - dare I say critical. Data providers often provide data with the stipulation that an attribution string be carried along with it, so for the OGI API to not provide a standardized way to do that would be a mistake. The good news is that it's an extremely simple element to define, I don't think it'll stir up any controversy.

[cmheazel]

A suggestion for use in the Sprint - Let's establish a library of metadata elements which can be included in a JSON response. This can consist of a single "metadata" object with no required properties. The "library" would be the list of properties associated with that object.
Note: this is proposed as an experiment. We can mature the concept if it shows promise.

[pvretano]

@pomakis rights and license fields might be nice too ...
@cmheazel that is the approach taken in OGC API Records; the list of "core queryables" is basically a list (or library) of properties (or metadata elements) that should appear in a catalogue record; some are mandatory others are recommended (see here)

[jerstlouis]

@pvretano I don't see an attribution in that list of core queryables, is there some other property covering that specifically, or is this something which should also be considered for Records?

[pvretano]

@jerstlouis I think it is covered between the publisher, rights, license fields ... no?

[jerstlouis]

@pvretano Well the idea for attribution is that it is the recommended or required text that a client could automatically display e.g. on the bottom corner of a map automatically.

The publisher might not be formatted as required or contain all required information; the license would be the long legal text, and rights might not include the necessary information either.

So I would say that no, those don't cover attribution (and I think this is the single most importance piece needed as far as the collection info resource goes).

[pvretano]

@jerstlouis do you have a specific definition of "attribution"? The only reference I could find to attribution in DCAT, for example, was qualified attribution and its definition was: Link to an Agent having some form of responsibility for the resource.

[jerstlouis]

@pvretano I don't have a specific definition, but the concept is precisely what @pomakis mentioned above:

Data providers often provide data with the stipulation that an attribution string be carried along with it, so for the OGI API to not provide a standardized way to do that would be a mistake.

[cmheazel]

Resolved in #174