Matches in Nanopublications for { ?s <https://w3id.org/fair/fip/terms/considerations> ?o ?g. }
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "The service was developed to allow publicly sharing the data models. Is a part of making the data models themselves FAIR." assertion.
- declaration considerations "" assertion.
- declaration considerations "" 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 "" assertion.
- declaration considerations "Instances of DLite datamodels include the URI of the metadata (i.e. the datamodel)." assertion.
- declaration considerations "It is possible to publish metadata records to be directly resolvable on http://onto-ns.com (through the entites-service) hosted by SINTEF. This requires the metadata uri to have a namespace starting with http://onto-ns.com. Other alternatives are github repositories and project dedicated services." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "Other protocols are allowed, such as sftp and https." assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "DLite works in conjunction with mapping to ontologies." 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 "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 "The datamodel is mapped to an ontology to achieve full semantic interoperability" assertion.
- declaration considerations "Eeach dataset is connceted 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 "We have versioning of ontologies and dlite datamodels. The ontologies themeselves should have metadata such as creator, constributor etc. EMMO does. For the DLite metadata records no provenance profiel ahs been chosen." 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 "" 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 "" 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.