Comments (11)
So ":a" is the dataset URI?
from bio2rdf-scripts.
a data item uri
from bio2rdf-scripts.
another option was adding the dataset namespace via dc:source
ns:id dc:source "namespace" ;
from bio2rdf-scripts.
Could you give an example how this would work for a concrete resource/dataset combination (say uniprot for example)? I am having trouble visualising it.
from bio2rdf-scripts.
refseq:54321 refseq_vocabulary:x-uniprot uniprot:Q12345 .
uniprot:Q12345
dc:identifer "Q12345" ; // or dc:identifier "uniprot:Q12345"
dc:source "uniprot" // or dc:source http://bio2rdf.org/uniprot
a uniprot_vocabulary:Resource
the value in having the dc literals in the above form is that they are indexed and can be used to construct a URI
from bio2rdf-scripts.
Okay, much clearer.
Up until recently dc:identifier was always "ns:id", so I would personally prefer, for backwards compatibility all the way back to the original Banff Manifesto, if we stayed with that convention. We could use another predicate to have just the "id" available as a literal.
dc:source is specified to provide a link from a resource to a related resource that the given resource is derived from. The specification recommends that a formal identification scheme be used, so "uniprot" isn't the clearest identification that we could have there. I would also prefer http://bio2rdf.org/dataset:uniprot or http://bio2rdf.org/dataset/uniprot or something similar to that, rather than http://bio2rdf.org/uniprot
http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#terms-source
from bio2rdf-scripts.
i don't know of anything that matches exactly then. we could do something
like
bio2rdf_vocabulary:source-identifier "Q12345"
bio2rdf_vocabulary:source-dataset "uniprot"
On Mon, Mar 25, 2013 at 11:27 PM, Peter Ansell [email protected]:
Okay, much clearer.
Up until recently dc:identifier as always "ns:id", so I would personally
prefer, for backwards compatibility all the way back to the original Banff
Manifesto, if we stayed with that convention. We could use another
predicate to have just the "id" available as a literal.dc:source is specified to provide a link from a resource to a related
resource that the given resource is derived from. The specification
recommends that a formal identification scheme be used, so "uniprot" isn't
the clearest identification that we could have there. I would also prefer
http://bio2rdf.org/dataset:uniprot or http://bio2rdf.org/dataset/uniprotor something similar to that, rather than
http://bio2rdf.org/uniprothttp://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#terms-source
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/198#issuecomment-15439042
.
Michel Dumontier
Associate Professor of Bioinformatics, Carleton University
Chair, W3C Semantic Web for Health Care and the Life Sciences Interest Group
http://dumontierlab.com
from bio2rdf-scripts.
Would the following be a useful compromise?
dcterms:identifier "uniprot:Q12345"
bio2rdf_vocabulary:source-identifier "Q12345"
bio2rdf_vocabulary:source-dataset "uniprot"
bio2rdf_vocabulary:source-dataset-uri <http://bio2rdf.org/dataset:uniprot>
Should we also recommend the usage of rdfs:label where possible to give a human readable label if we can retrieve one? This would make scripts a lot slower but it may be useful enough to justify the additional requests.
rdfs:label "Ino eighty subunit 3"
from bio2rdf-scripts.
On Mon, Mar 25, 2013 at 11:50 PM, Peter Ansell [email protected]:
Would the following be a useful compromise?
dcterms:identifier "uniprot:Q12345"
bio2rdf_vocabulary:source-identifier "Q12345"
bio2rdf_vocabulary:source-dataset "uniprot"
bio2rdf_vocabulary:source-dataset-uri http://bio2rdf.org/dataset:uniprotthe alternative here is to put
a uniprot_vocabulary:Resource.
and when RDFizing the resource we'll see void:inDataset
Should we also recommend the usage of rdfs:label where possible to give a
human readable label if we can retrieve one? This would make scripts a lot
slower but it may be useful enough to justify the additional requests.rdfs:label "Ino eighty subunit 3"
this is questionable - should we generate a label when we're not processing
the dataset in which it is described? The problem is if the source dataset
changes to the label, we'll see multiple values if we merge the graphs.
That being said, sometimes that dataset does provide us with labels that
might be otherwise hard to get.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/198#issuecomment-15439603
.
Michel Dumontier
Associate Professor of Bioinformatics, Carleton University
Chair, W3C Semantic Web for Health Care and the Life Sciences Interest Group
http://dumontierlab.com
from bio2rdf-scripts.
ok, so let us allow the assertion of a label for an xref identifer provided by a third-party as an rdfs:label "text [ns:id]", but also mandate dc:title "text" in the primary dataset. that way if there is an inconsistency in label, we can fall back to dc:title as the dataset-specific one.
from bio2rdf-scripts.
Sounds good to me.
from bio2rdf-scripts.
Related Issues (20)
- PharmGKB drug parse needs update
- PharmGKB disease parse needs update
- types in PharmGKB relationships
- Variation in KEGG URIs
- PharmGKB Variant data parsing needs to be revised
- PharmGKB pathway download not functional HOT 2
- Erroneous label for drugbank type
- Hash URIs for Drugbank HOT 2
- Error in KEGG link generation HOT 2
- spaces in URIs and unescaped back slashes in the generated output for DRUGBANK HOT 4
- drugbank: protein group problem
- backslash characters in clinicaltrials HOT 4
- XML parse error for clinicaltrials HOT 1
- Malformed Links HOT 1
- WikiPathways license in datasets documentation is outdated HOT 1
- Drugbank drug-target interactions HOT 4
- How can I parse the Drugbank.nq.gz? HOT 2
- dataset hyperlink not functional??? HOT 1
- Link to v3 release notes broken HOT 1
- Inquiry about using bio2rdf to parse drugbank HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bio2rdf-scripts.