Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "We have unique identifiers in the KB, persistence beyond the project is yet to be clarified. Also, the IRIs are not directly resolvable, but they are findable in the KB. The algorithm for generation of unique identifiers will be specified in the Pink KB documentation." assertion.
- declaration considerations "" assertion.
- declaration considerations "We have unique identifiers in the KB, persistence beyond the project is yet to be clarified. Also, the IRIs are not directly resolvable, but they are findable in the KB. There is a difference between dcat:datasets and dcat:distributions, and this is taken care of in the PINK KB. " assertion.
- declaration considerations "Datasets are currently being published on Zenodo, figshare and similar services providing DOIs. Note that these are dcat distributions. This solution will not be used for confidential data. " assertion.
- declaration considerations "The PINK Annotation Schema is for now a list of terms, that will eventually become a more structured vocabulary and ideally directly connected to proper ontologies. The full connection to Ontologies will be done for most terms if not all. By connecting to ontologies, findability will be greatly enhanced." assertion.
- declaration considerations "This makes use of SKOS, RDFS, RDF and several other vocabularies. These could be added as FERs here as well." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "The Tripper Annotation schema builds on DCAT." assertion.
- declaration considerations "DLite provides a schema links data to the structural metadata needed for interoperability." assertion.
- declaration considerations "" assertion.
- declaration considerations "The PINK KB provides information about where to go to fetch the data. Teh actual data will be provided in various databases etc. depending on intended avilablity and type of data. This FIP does not force rule on where to publish of the actual datasets." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Defined in the PINKISH specficitions (not openly available). https://github.com/PINK-project/pinkish/blob/main/SPECIFICATION.md" assertion.
- declaration considerations "Depends on the dataset provider." assertion.
- declaration considerations "Ideally, there will be a service running at the end of the project available. However, longterm maintenance of this is not yet secured. At project end, the PINK KB, will be at minimum serialised and stored in the PINK project reopsitory. Also, after evaluation of IP, it might be published openly on persistent services hosted within EU, such as Zenodo. " assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "In order to obtain machine interoperability at the numerical level for data, DLite plugins are created to match DLite datamodels and the data as provided in the preferred format by the creator/curator of the data." assertion.
- declaration considerations "Datamodels are not annotated by mappings to ontologies." assertion.
- declaration considerations "And relevant EMMO-based ontologies." assertion.
- declaration considerations "Datasets are annotated with the PINK annotation schema which is based on the Tripper core annotation schema. This latter uses DCAT-AP as standard for annotating resources." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Eeach dataset is connected to a given dlite datamodel, following the schema defined therein. Convertion between datasets and the datamodel is done through user implemented plugins. Semantic intereoperability is achieved through mappings to ontologies." assertion.
- declaration considerations "We will probably have one licence for the PINK knowledge base, i.e. for the metadata in the knowledge base. " assertion.
- declaration considerations "The license for data is dependent on the choice of each data provider/owner. The license will be defined with dcterms:license in the knowledge base." assertion.
- declaration considerations "The tripper annotation schema includes fields that identify curators of the dataset, and it rquires that metadata creators are added as curators." assertion.
- declaration considerations "DC-terms are used witht he addition of PROV-O terms as suggested by DCAT-AP" assertion.
- declaration considerations "DC-terms are used witht he addition of PROV-O terms as suggested by DCAT-AP" assertion.
- declaration considerations "" assertion.
- declaration considerations "EMMO provenance specifications are included in the PINK Annotation Schema, as an option for enhances semantics. These annotations are found in the persistence (https://w3id.org/emmo/perspectives/persistence) and workflows (https://w3id.org/emmo/reference/workflow) modules in EMMO." assertion.
- declaration considerations "A Handle PID is assigned to all data products and instruments" assertion.
- declaration considerations "DataCite DOI are assigned to datasets and software" assertion.
- declaration considerations "Used to identify people contributing to the processes of data creation, collection and curation" assertion.
- declaration considerations "Used to identify involved institutions" assertion.
- declaration considerations "A Handle PID is assigned to all data products and instruments" assertion.
- declaration considerations "DataCite DOIs are assigned to datasets and software" assertion.
- declaration considerations "Used to identify people contributing to the processes of data creation, collection and curation" assertion.
- declaration considerations "Used to identify involved institutions" assertion.
- declaration considerations "DataCite metadata schema is used for data collections" assertion.
- declaration considerations "All our (meta)data are NetCDF 1.7 compliant. The definition of new CF variable names has been approved by the CF community" assertion.
- declaration considerations "ACTRIS Metadata schema is an extension of the WMO Core Profile" assertion.
- declaration considerations "ACTRIS Metadata schema is an extension of the ISO 19115" assertion.
- declaration considerations "Collections of data" assertion.
- declaration considerations "Data products and instruments" assertion.
- declaration considerations "Collections of data" assertion.
- declaration considerations "Used for legacy datasets" assertion.
- declaration considerations "ACTRIS ARES Data Portal registered on Re3Data repository" assertion.
- declaration considerations "ACTRIS Data Portal " assertion.
- declaration considerations "ACTRIS-ARES Data Portal & API" assertion.
- declaration considerations "Collections of data" assertion.
- declaration considerations "Legacy datasets" assertion.
- declaration considerations "ACTRIS ARES Data Portal registered on Re3Data repository" assertion.
- declaration considerations "ACTRIS-ARES Data Portal & API" assertion.
- declaration considerations "RESTful API" assertion.
- declaration considerations "RESTful API" assertion.
- declaration considerations "THREDDS catalog" assertion.
- declaration considerations "RESTful API" assertion.
- declaration considerations "Internal data transfer" assertion.
- declaration considerations "THREDDS catalog" assertion.
- declaration considerations "All ACTRIS ARES data are accessible without authentication" assertion.
- declaration considerations "All ACTRIS ARES data are accessible without authentication" assertion.
- declaration considerations "ACTRIS Data Policy" assertion.
- declaration considerations "Metadata in JSON format through REST API" assertion.
- declaration considerations "ACTRIS vocabulary" assertion.
- declaration considerations "NetCDF 1.7 compliance" assertion.
- declaration considerations "Under discussion" assertion.
- declaration considerations "CF variable names" assertion.
- declaration considerations "ACTRIS vocabulary" assertion.
- declaration considerations "All ACTRIS ARES variables are CF compliant" assertion.
- declaration considerations "NetCDF compliant with Climate and Forecasts (CF) Metadata Convention v1.7" assertion.
- declaration considerations "ACTRIS Vocabulary" assertion.
- declaration considerations "All ACTRIS ARES variables are CF compliant" assertion.
- declaration considerations "" assertion.
- declaration considerations "ACTRIS Vocabulary" assertion.
- declaration considerations "NetCDF compliant with Climate and Forecasts (CF) Metadata Convention v1.7" assertion.
- declaration considerations "ACTRIS Vocabulary" assertion.