P-Rec.5: Semantic repositories must offer access to Semantic Artefacts and their content using community standard APIs and serializations to support both use/ reuse and indexation by search engines. (D2.5) #32
Semantic artefacts are distributed across the web in a variety of locations and formats. Semantic repositories act as aggregators of semantic artefact publishing both the metadata and the content of the semantic artefacts and providing a search engine and an API to search and access the content through dedicated services. However, the APIs to search and access content is specific to each repository which hampers the possibility to access content from multiple sources for use and reuse but also for indexing by search engine. Part of the API heterogeneity is linked with the diverse metadata schema used by repositories to describe semantic artefacts.
To enable federated searches across repositories, it is necessary to harmonize the API landscape by defining a common set of API features, based on a common minimum set of metadata for describing semantic artefacts (see P-Rec. 3). See examples below for more details.
This recommendation does not aim to support any particular solution, but emphasizes the need for the community of semantic repositories to agree on a portfolio of common solutions.
Semantic artefacts are distributed across the web in a variety of locations and formats. Semantic repositories act as aggregators of semantic artefact publishing both the metadata and the content of the semantic artefacts and providing a search engine and an API to search and access the content through dedicated services. However, the APIs to search and access content is specific to each repository which hampers the possibility to access content from multiple sources for use and reuse but also for indexing by search engine. Part of the API heterogeneity is linked with the diverse metadata schema used by repositories to describe semantic artefacts.
To enable federated searches across repositories, it is necessary to harmonize the API landscape by defining a common set of API features, based on a common minimum set of metadata for describing semantic artefacts (see P-Rec. 3). See examples below for more details.
This recommendation does not aim to support any particular solution, but emphasizes the need for the community of semantic repositories to agree on a portfolio of common solutions.