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 "" 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. In the project data will be stored in several different locations that provide URIs, e.g. data.sintef.no and zenodo. Each user has a freedom of choice here, and the DYNCAT KB serves as the common source of knowledge. There is a difference between dcat:datasets and dcat:distributions, and this is taken care of in the DYNCAT KB. " assertion.
- declaration considerations "This is dependent on the data storage provider, e.g. zenodo or data.sintef.no" assertion.
- declaration considerations "The metadata ontology will be created with Protege, supported by tripper and emmontopy and manually curated in text editors. This will be done by experts. Furthermore, DataDocWeb might implement functionality for users to suggest new classes, but this will be at a later date. " assertion.
- declaration considerations "The DYNCAT KB will contain information about where and how to access the actual data that is described with metadata in the DYNCAT KB." assertion.
- declaration considerations "The persistency policy for data is determined by the data storage service. Data produced in the project must be kept available for at least 10 years. For metadata, persistency of the knowledge base is not yet decided beyond the project duration. However, at least a serialised version of the knowledge base wil be stored by the project owner for the same duration." assertion.
- declaration considerations "The final storage facility for data produced in the DYNCAT is not yet specified. It may be in internal servers hosted by SINTEF/NTNU. How to access these data will be described in the metadata (DYNCAT KB)." assertion.
- declaration considerations "Tripper provides an API to interact easily with the knowledge ase. The knwoledge base will have a SPARQL WEB-API." assertion.
- declaration considerations "The current architecture suggestion places the DYCNAT KB behind a SINTEF A&A service." assertion.
- declaration considerations "Data will certainly be communicated/shared in the SINTEF workspace created for the DYNCAT project. Implementation choices for creation of machine accessible databases are yet to be decided within the project. " 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 DYNCAT KB, will be at minimum serialised and stored in the DYNCAT project reopsitory (hosted by SINTEF). Also, after evaluation of IP, it might be published openly on persistent services hosted within EU/Norway, such as Zenodo. " assertion.
- declaration considerations "The DYNCAT KB is a triplestore populated by RDF triples." assertion.
- declaration considerations "EMMO and domain/application ontologies are expressed in OWL." assertion.
- declaration considerations "DLite datamodels will be used to descrbed data at the numerical level. Mapping to ontologies will provide interoperability and the conceptual level." assertion.
- declaration considerations "This is not done by an online service, but by using the tools that we have implemented for easier documentation of data, Tripper and its dependencies (rdflib and pyld), which are python libraries. " assertion.
- declaration considerations "Datasets are described by DLite datamodels which are linked/mapped to ontological concepts and made interoperable with parsers/generators." assertion.
- declaration considerations "Datasets are described by DLite datamodels which are linked/mapped to ontological concepts and made interoperable with parsers/generators." assertion.
- declaration considerations "Protege for ontology creation and visualisation. EMMOntoPy for ontology creation and validation. Text editors." assertion.
- declaration considerations "The DYNCAT annotation schema expands on the Tripper annotation schema which is based on the DCAT annotation schema. " assertion.
- declaration considerations "Full semantics is ensured by mapping the DLite model to an ontology." assertion.
- declaration considerations "We understand this as mappings from the Dlite datamodels to the ontologies. Json-ld context is also used for mappings." assertion.
- declaration considerations "Text editors. Spreadsheet editors." assertion.
- declaration considerations "To be decided." assertion.
- declaration considerations "To be decided. There will not be a unique choice on datasets." assertion.
- declaration considerations "No choice have been made yet." assertion.
- declaration considerations "Tripper combines EMMO and Prov-O so that it is technically feasible to document provenance of both existing data and planned data (e.g. expected provenance from a specified workflow)." assertion.
- declaration considerations "Tripper combines EMMO and Prov-O so that it is technically feasible to document provenance of both existing data and planned data (e.g. expected provenance from a specified workflow)." assertion.
- declaration considerations "We understand this question as part of interoperatbility. We have chosen DLite for intereoperability. Due to the nature of th data being very similar, we will alsp use ase." assertion.
- declaration considerations "We can use AI, but strictly supervised, to suggest metadata, vocabularies and mappings. " 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 "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.
- declaration considerations "" assertion.