Übersicht:
Favoritenliste:
Favoritenseiten
Ihre Favoritenliste enthält derzeit keine Seiten. Sie fügen dieser Liste Seiten hinzu, indem Sie im Menü Extras der angezeigten Seite Favorit selektieren. |
meeting minutes/notes
# recap of the process, status of work
# proposals for approach
Just a comment: In Germany we use the gmd:protocol to describe the type of the service ( WMS / WFS / WCS / WPS / ATOM / FILE) and the gmd:applicationProfil to specify the media type.
# discussion
If you use the gmd-description element to referenced an access- or endPoint, which iso-element are you use to specify e.g. the EPSG code (which is supported by the service)?
... the EPSG information can be 'left' to the service capabilities
Which URL should referenced in the extendedCapabilities of the service? Right now it's the link to service metadata.
In principle, the idea is that the extended capabilitie section disappears, and there will be no service metadata at all if we use this simplified approach.
Is there a possibility to link to service-md in the standard getCap section (without extension) - could be useful
How should we handle the fact, if a user create a service on different datasets (the basic idea of open data)?
If a service works base on more than one dataset, each dataset metadata point to the same service and from service capabilities is access to metadata of all datasets which the service base on.
No, if there are different providers, the service will not be referenced in the dataset.
You are right, but it is issue of organization of national infrastructure, providers should talk together :)
Good point, but I think a bit wider ... the approach of open data is, that every one can share and use the available data ...
= further discussion to all points on GitHub (creating an issue per topic, help to converge on the final approach)
# next steps
= next meeting: