You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
- This closesopengeospatial#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.
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.
The text was updated successfully, but these errors were encountered: