some suggestions for lessons learned #1
Description
- Registries, and especially the base registries, need proper uri management. Records should be made available on a unique persistent uri, so other registries can use those uri's to create links between the registries.
- Be aware that you don't just publish data on the web, by doing so you create data on the web, others will start to link to your data, thus creating added value for your data
- Each data community (geospatial, linked data, governmental data, search engines, web/app developers, statistics) has it's own data sharing conventions. To properly serve each of them, separate endpoints for the same data is optimal from a consumption perspective. By doing so you potentially create multiple identifiers for the same data object.
- Using content negotiation is fine to serve multiple encodings from a single endpoint, but gets a challenge when you want to serve the data transformed in multiple schema's/ontologies. Linked data suggests to annotate data using multiple ontologies within a single document, but this is barely accepted in other communities such as search engines, iso19139 etc.
- The fact that search engines are a black box makes it really unpredictable and labor-intensive to use them as part of a study. It would be better to create a new search engine to demonstrate what search engines will be able to achieve in future.
- CSW, WFS, GML, iso19139, INSPIRE conventions are quite fit for being used as a base for a linked-data-proxy-approach, most of the challenges are in how the standards are currently (poorly) implemented in various implementations