Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more information about support for licenses in OGC API - Common - Part 2 #301

Closed
ghobona opened this issue Feb 24, 2022 · 0 comments
Closed
Labels
Part 2 Issues to be resolved prior to TC vote

Comments

@ghobona
Copy link
Contributor

ghobona commented Feb 24, 2022

There is not much information about support for license information in Part 2. There is only mention of the relation type.

OGC API - Features - Part 1 (OGC 17-069r3) provides more information and includes Recommendation 10 (/rec/core/fc-md-license) which could be pulled into OGC API - Common - Part 2.

Example 4 in OGC API - Features - Part 1 also includes an example serialisation that could also be pulled into OGC API - Common - Part 2.

@cmheazel cmheazel added the Part 2 Issues to be resolved prior to TC vote label Jun 5, 2022
jerstlouis added a commit to jerstlouis/ogcapi-common that referenced this issue Sep 24, 2024
- This closes opengeospatial#301 and opengeospatial#338
- The following core record properties from Records were added:
  - keywords (also in 2DTMS & Tileset metadata model)
  - license (addresses opengeospatial#301; also in 2DTMS&TSMD)
  - resourceLanguages (also in 2DTMS&TSMD as simple strings)
  - formats (corresponding to mediaType in 2DTMS&TSMD as simple strings)
  - contacts (corresponding to pointOfContact in 2DTMS&TSMD as simple strings)
  - themes (also in 2DTMS&TSMD as simple strings)
  - rights
- The following properties were added from 2DTMS & TSMD:
  - epoch (of the native CRS)
  - geoDataClasses
  - created
  - updated
  - accessConstraints
  - publisher
- The other properties mentioned in opengeospatial#338 were already there.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Part 2 Issues to be resolved prior to TC vote
Projects
Development

No branches or pull requests

2 participants