le data model).
>>
>> best,
>> Andrea
>>
>>
>>
>> --
>> Richard D Boyce, PhD
>> Assistant Professor of Biomedical Informatics
>> Faculty, Center for Pharmaceutical Policy and Prescribing
>> Faculty, Geriatric Pharmaceutical Outcomes and Gero-Informatics Research and
>> Training Program
>> University of pittsburghrd...@pitt.edu
>> Office: 412-648-9219
>> Twitter: @bhaapgh
>>
>>
>
>
> --
> Mikel Egaña Aranguren, Ph.D.
>
> http://mikeleganaaranguren.com
>
>
>
--
Jerven Bolleman
m...@jerven.eu
w this could be inferred from the truth value of a
>> bit.
>>
>
> By documenting the property so as to make that explicit. How else do we
> understand any property value?
>
> -Alan
>
--
Jerven Bolleman
m...@jerven.eu
ly you don't know the license, but you also don't know why you
>>> don't know, it is indeed hard to say anything about the license.
>>>
>>> If all you want to say is who grants the license, you might want to
>>> consider something like:
>>>
>>> ex:myData ex:canBeLicensedForEndUseBy ex:EBI
>>>
>>> Best,
>>> Oliver
>>>
>>>
>>> --
>>> Oliver Ruebenacker
>>> Founder at Relomics Consulting
>>> Be always grateful, but never satisfied.
>>
>>
>
--
Jerven Bolleman
m...@jerven.eu
provided. (We are closing the world in certain areas.)
>
> Our proposed solution is written up at
> https://github.com/joejimbo/HCLSDatasetDescriptions/issues/65
>
> Alasdair
>
> On 2 Jun 2014, at 16:47, Jerven Bolleman wrote:
>
> Hi Alasdair,
>
> It is good practice in
ram even with OmniGraffle installed.
>>>
>>> On Wed, Apr 16, 2014 at 11:31 AM, Thomas Steiner wrote:
>>> > http://lod-cloud.net/#workflow :-)
>>> >
>>> > --
>>> > Thomas Steiner, Employee, Google Inc.
>>> > http://blog.tomayac.com, http://twitter.com/tomayac
>>> >
>>> > -BEGIN PGP SIGNATURE-
>>> > Version: GnuPG v1.4.12 (GNU/Linux)
>>> >
>>> >
>>> > iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtP5://xKcd.c0m/1181/
>>> > -END PGP SIGNATURE-
>>>
>>
>
--
Jerven Bolleman
m...@jerven.eu
ate
> alasdair.g...@manchester.ac.uk
>
> http://www.cs.man.ac.uk/~graya/
>
> Please consider the environment before printing this email.
>
>
>
--
Jerven Bolleman
m...@jerven.eu
3rd try now without attachments as some SPAM filter seems to reject this
mail.
Hope not everyone gets 4 copies now :(
Regards,
Jerven
-- Forwarded message --
From: Jerven Bolleman
Date: Mon, Jun 3, 2013 at 9:57 PM
Subject: Fwd: Question about Semantic Web
To: public-semweb
r/bio2rdf-release-2-improved-coverage-interoperability-and-provenance-of-linked-data-for-the-life-sciences
>
>
>
>
> On Tue, Jun 4, 2013 at 3:23 PM, Jerven Bolleman wrote:
>
>>
>>
>>
>> On Tue, Jun 4, 2013 at 3:05 PM, Michel Dumontier <
>> michel.dumont.
On Tue, Jun 4, 2013 at 3:05 PM, Michel Dumontier wrote:
>
>
>
> On Tue, Jun 4, 2013 at 2:40 PM, Jerven Bolleman wrote:
>
>>
>>
>>
>> On Tue, Jun 4, 2013 at 11:36 AM, Alasdair J G Gray <
>> alasdair.g...@manchester.ac.uk> wrote:
>>
>
e.g. can we think of something that can prevent.
uniprot:P12345 a up:Sequence .
sequence:P12345 a up:Protein .
And is a dataset description the right place for this validation data?
Regards,
Jerven
>
>
> On Tue, Jun 4, 2013 at 3:01 PM, Joachim Baran wrote:
>
>
On Tue, Jun 4, 2013 at 2:52 PM, Michel Dumontier wrote:
>
>
>
> On Tue, Jun 4, 2013 at 2:47 PM, Jerven Bolleman wrote:
>
>> Hi All,
>>
>> The problem with the current suggested solution is that it does not
>> account for a mix of identifiers in a dat
>> templates for resolving relevant identifiers, and provides regexps for
>> validating the syntax of identifiers.
>>
>> I think that the GO xrefs are extremely useful and would be on Michel's
>> side on including them.
>>
>> Best wishes,
>> Joachim
>>
>
>
> --
> --**--
> Nick Juty
> Database Curator
> European Bioinformatics Institute
> Cambridge, United Kingdom
> --**--
>
>
--
Jerven Bolleman
m...@jerven.eu
data.
>
Of course I don't disagree with the usecase. I disagree with the chosen
solution because it is on the wrong level of granularity.
> Alasdair
>
> Dr Alasdair J G Gray
> Research Associate
> alasdair.g...@manchester.ac.uk
> +44 161 275 0145
>
> http://www.cs.man.ac.uk/~graya/
>
> Please consider the environment before printing this email.
>
>
--
Jerven Bolleman
m...@jerven.eu
ll as addressing the
> provenance section.
>
> Attached are the notes I made during today's call.
>
> Alasdair
>
>
>
> Dr Alasdair J G Gray
> Research Associate
> alasdair.g...@manchester.ac.uk
> +44 161 275 0145
>
> http://www.cs.man.ac.uk/~graya/
&g
rds is an potential issue in all labs.
> Make the
> distinctions you care about. Let others make the distinctions that they
> care about.
Agree, just identify your distinction! Also the data format is not the
user interface (or at least it should not be so in an ideal world)
Jerven
>
> Phi
e disagree.
>>
>>
>> Since this assertion (that this position is a G) is made with a few
>> million similar assertions, all of which have some element of doubt - it
>> would be highly surprising if every single call were correct: yet within the
>> logic of RDF we probably end up asserting the truth of the whole graph …
>> which leads us onto the dangerous path of ex contradictione quadlibet
>>
>>
>>
>>
>>
>>
>>
>>
>
>
--
Jerven Bolleman
m...@jerven.eu
ibes Bio2RDF resources.
>
> Cheers,
> Scott
>
> --
> M. Scott Marshall, PhD
> MAASTRO clinic, http://www.maastro.nl/en/1/
> http://eurecaproject.eu/
> https://plus.google.com/u/0/114642613065018821852/posts
> http://www.linkedin.com/pub/m-scott-marshall/5/464/a22
--
Jerven Bolleman
m...@jerven.eu
t;> --
>
>
>
>
> --
> Michel Dumontier
> Associate Professor of Bioinformatics, Carleton University
> Chair, W3C Semantic Web for Health Care and the Life Sciences Interest Group
> http://dumontierlab.com
--
Jerven Bolleman
m...@jerven.eu
>
>
> *NOTICE TO RECIPIENT:* If you are not the intended recipient of this
> e-mail, you are prohibited from sharing, copying, or otherwise using or
> disclosing its contents. If you have received this e-mail in error, please
> notify the sender immediately by reply e-mail and pe
not
> expressly made on behalf of Macmillan Publishers Limited or one of its
> agents.
> Please note that neither Macmillan Publishers Limited nor any of its agents
> accept any responsibility for viruses that may be contained in this e-mail
> or
> its attachments and it is your responsibility to scan the e-mail and
> attachments (if any). No contracts may be concluded on behalf of Macmillan
> Publishers Limited or its agents by means of e-mail communication.
> Macmillan
> Publishers Limited Registered in England and Wales with registered number
> 785998
> Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS
>
>
>
>
>
--
Jerven Bolleman
m...@jerven.eu
contains all UniProt data including UniParc and
UniRef as well as the NCBI/UniProt taxonomy for querying.
Regards,
Jerven Bolleman
--
---
Jerven Bollemanjerven.bolle...@isb-sib.ch
Swiss Institute of
It does not look like there is an official mesh distribution in RDF at
this time.
http://www.nlm.nih.gov/mesh/filelist.html
Regards,
Jerven Bolleman
On Mon, Jun 6, 2011 at 4:05 PM, Matt Vagnoni wrote:
> Is this the official MeSH base uri?
>
> ...from phone
>
> On Jun 6, 2011 8:3
orial. TopBraid Composer was widely touted. A few
>> encouraging news items: Nicolas Le Novere told us that MIRIAM
>> identifiers will go to URIs (from URNs) and Jerven Bolleman told us
>> that Uniprot is getting a SPARQL endpoint for their RDF. There was a
>> strong pharm
23 matches
Mail list logo
