Announcement: PAV (Provenance, Authoring and Versioning) ontology 2.3.0

I am proud to announce the release of PAV (Provenance, Authoring and Versioning) ontology version 2.3.0. PAV is a lightweight ontology for tracking Provenance, Authoring and Versioning. PAV specializes the W3C provenance ontology PROV-O in order to describe authorship, curation and digital

Re: owl:sameAs - Harmful to provenance?

On 4/9/13 1:25 PM, Michel Dumontier wrote: And the same can be said for teaching people how to construct *useful* ontologies (in OWL or any other language for that matter). If the principles are simple and coherent, then the execution will be straightforward and effective. Yes! No problem wit

Re: owl:sameAs - Harmful to provenance?

And the same can be said for teaching people how to construct *useful* ontologies (in OWL or any other language for that matter). If the principles are simple and coherent, then the execution will be straightforward and effective. m. On Tue, Apr 9, 2013 at 1:18 PM, Kingsley Idehen wrote: > On 4

Re: owl:sameAs - Harmful to provenance?

On 2013-04-09, at 12:40 PM, phillip.l...@newcastle.ac.uk (Phillip Lord) wrote: > RDF is nice. It's useful. It will remain useful, at least if people are > allowed to use it without being told that they are doing it all wrong. Completely out of context: I second that notion. I rather go throug

Re: owl:sameAs - Harmful to provenance?

On 4/9/13 12:40 PM, Phillip Lord wrote: Kingsley Idehen writes: On 4/9/13 11:31 AM, Phillip Lord wrote: Compare all you like. RDF is just another technology; it's not going to let me do anything that I cannot do in another way. So you are questioning its unique selling points, I assume? No.

Re: owl:sameAs - Harmful to provenance?

Kingsley Idehen writes: > On 4/9/13 11:31 AM, Phillip Lord wrote: >> Compare all you like. RDF is just another technology; it's not going to >> let me do anything that I cannot do in another way. > So you are questioning its unique selling points, I assume? No. I don't care. I just care whether

Re: owl:sameAs - Harmful to provenance?

On 4/9/13 11:31 AM, Phillip Lord wrote: Compare all you like. RDF is just another technology; it's not going to let me do anything that I cannot do in another way. So you are questioning its unique selling points, I assume? If so, can you point us to a technology that addresses the issue of grou

Re: owl:sameAs - Harmful to provenance?

p.l...@newcastle.ac.uk] >> Sent: Monday, April 08, 2013 9:53 AM >> To: Oliver Ruebenacker >> Cc: David Booth; Pat Hayes; Peter Ansell; Alan Ruttenberg; > public-semweb- >> lifesci >> Subject: Re: owl:sameAs - Harmful to provenance? >> >> >> And it is

Re: owl:sameAs - Harmful to provenance?

for 'data' >> >> http://www.biomedcentral.com/1471-2105/12/487 and >> http://xpdb.nist.gov/chemblast/pdb.pl and >> http://www.nature.com/nmeth/journal/v9/n7/abs/nmeth.2084.html >> >> T N Bhat >> >> -Original Message- >> From

Re: owl:sameAs - Harmful to provenance?

Oliver Ruebenacker writes: > Hello Philip, Phillip:-) > Apparently, you are confusing two different cases. I talked about the > same reference meaning two different things. You are talking about > different references talking about the same thing. No. dc:creator means many different things.

Re: owl:sameAs - Harmful to provenance?

On Apr 8, 2013, at 7:07 AM, David Booth wrote: > Hi Pat, > > On 04/04/2013 02:03 AM, Pat Hayes wrote: >> >> On Apr 3, 2013, at 9:00 PM, Peter Ansell wrote: >> >>> On 4 April 2013 11:58, David Booth wrote: On >>> 04/02/2013 05:02 PM, Alan Ruttenberg wrote: On Tuesday, April 2, >>> 2013, David

Re: owl:sameAs - Harmful to provenance?

Hi Rich, On 04/08/2013 02:08 PM, Rich Cooper wrote: Dear David, You wrote: 1. Owen's URI definition will always be ambiguous. There will always exist a property p such that neither p nor its negation are entailed by the URI definition. While true, this leaves out the subjectiv

Re: owl:sameAs - Harmful to provenance?

Hi Oliver, On 04/08/2013 11:55 AM, Oliver Ruebenacker wrote: Hello David, all, What I hear you saying is primarily that: 1. It is possible to have sets of assertions such that each set is consistent, but the union is contradictory. Yes, even with all parties acting intelligently

Re: owl:sameAs - Harmful to provenance?

On Mon, Apr 8, 2013 at 2:23 PM, Alan Ruttenberg wrote: > > > > On Mon, Apr 8, 2013 at 2:10 PM, Michel Dumontier < > michel.dumont...@gmail.com> wrote: > >> >> >> >> On Mon, Apr 8, 2013 at 1:23 PM, Alan Ruttenberg > > wrote: >> >>> Nicely pointed out, TN. >>> >>> Thinking about "metadata" as some o

Re: owl:sameAs - Harmful to provenance?

On Mon, Apr 8, 2013 at 2:10 PM, Michel Dumontier wrote: > > > > On Mon, Apr 8, 2013 at 1:23 PM, Alan Ruttenberg > wrote: > >> Nicely pointed out, TN. >> >> Thinking about "metadata" as some other category of data is usually a bad >> sign. I've often found it to mean, in practice, "data I care le

Re: owl:sameAs - Harmful to provenance?

On Mon, Apr 8, 2013 at 1:23 PM, Alan Ruttenberg wrote: > Nicely pointed out, TN. > > Thinking about "metadata" as some other category of data is usually a bad > sign. I've often found it to mean, in practice, "data I care less about". > > Phil, to make the case that RDF helps here, we would want t

RE: owl:sameAs - Harmful to provenance?

3 AM > To: Oliver Ruebenacker > Cc: David Booth; Pat Hayes; Peter Ansell; Alan Ruttenberg; public-semweb- > lifesci > Subject: Re: owl:sameAs - Harmful to provenance? > > > And it is this bit -- "before we can do anything useful" that is utterly > wrong. > > R

Re: owl:sameAs - Harmful to provenance?

meth/journal/v9/n7/abs/nmeth.2084.html > > T N Bhat > > -Original Message- > From: Phillip Lord [mailto:phillip.l...@newcastle.ac.uk] > Sent: Monday, April 08, 2013 12:53 PM > To: Oliver Ruebenacker > Cc: David Booth; Pat Hayes; Peter Ansell; Alan Ruttenberg; > publi

RE: owl:sameAs - Harmful to provenance?

.l...@newcastle.ac.uk] Sent: Monday, April 08, 2013 12:53 PM To: Oliver Ruebenacker Cc: David Booth; Pat Hayes; Peter Ansell; Alan Ruttenberg; public-semweb-lifesci Subject: Re: owl:sameAs - Harmful to provenance? And it is this bit -- "before we can do anything useful" that is utterly w

Re: owl:sameAs - Harmful to provenance?

Hello Philip, Apparently, you are confusing two different cases. I talked about the same reference meaning two different things. You are talking about different references talking about the same thing. Confusion is the enemy of understanding. Take care Oliver On Mon, Apr 8, 2

Re: owl:sameAs - Harmful to provenance?

And it is this bit -- "before we can do anything useful" that is utterly wrong. Recently I have spent a lot of time look at Dublin Core creator fields. You could not believe how many different ways they are used. String literals ("Phillip Lord"), last-first ("Lord, Phillip"), with abbrevs ("P. L

Re: owl:sameAs - Harmful to provenance?

Hello David, all, What I hear you saying is primarily that: 1. It is possible to have sets of assertions such that each set is consistent, but the union is contradictory. 2. If I don't know the meaning of these assertions, I can't prove that they are unjustified. That's pretty obvio

Re: owl:sameAs - Harmful to provenance?

Hi Pat, On 04/04/2013 02:03 AM, Pat Hayes wrote: On Apr 3, 2013, at 9:00 PM, Peter Ansell wrote: On 4 April 2013 11:58, David Booth wrote: On 04/02/2013 05:02 PM, Alan Ruttenberg wrote: On Tuesday, April 2, 2013, David Booth wrote: On 03/27/2013 10:56 PM, Pat Hayes wrote: On Mar 27, 2013, at

Re: owl:sameAs - Harmful to provenance?

On 4/4/13 9:38 AM, Kingsley Idehen wrote: On 4/4/13 1:43 AM, Alan Ruttenberg wrote: Dropping Jim from cc in deference to him finishing his defense. On Wed, Apr 3, 2013 at 9:58 PM, David Booth > wrote: On 04/02/2013 05:02 PM, Alan Ruttenberg wrote: On Tue

Re: owl:sameAs - Harmful to provenance?

On 4/4/13 1:43 AM, Alan Ruttenberg wrote: Dropping Jim from cc in deference to him finishing his defense. On Wed, Apr 3, 2013 at 9:58 PM, David Booth > wrote: On 04/02/2013 05:02 PM, Alan Ruttenberg wrote: On Tuesday, April 2, 2013, David Booth wrote:

Re: owl:sameAs - Harmful to provenance?

David Booth writes: > Maybe someone can see a way to avoid this dilemma. Maybe > someone can figure out a way to distinguish between the > "essential" properties that serve to identify a resource, and > other "inessential" properties that the resource might have. > If so, and the number of "essen

Re: owl:sameAs - Harmful to provenance?

On Apr 3, 2013, at 9:00 PM, Peter Ansell wrote: > On 4 April 2013 11:58, David Booth wrote: > On 04/02/2013 05:02 PM, Alan Ruttenberg wrote: > On Tuesday, April 2, 2013, David Booth wrote: > On 03/27/2013 10:56 PM, Pat Hayes wrote: > On Mar 27, 2013, at 7:32 PM, Jim McCusker wrote: >

Re: owl:sameAs - Harmful to provenance?

Dropping Jim from cc in deference to him finishing his defense. On Wed, Apr 3, 2013 at 9:58 PM, David Booth wrote: > On 04/02/2013 05:02 PM, Alan Ruttenberg wrote: > >> On Tuesday, April 2, 2013, David Booth wrote: >> On 03/27/2013 10:56 PM, Pat Hayes wrote: >> On Mar 27, 2013, at 7:

Re: owl:sameAs - Harmful to provenance?

On 4 April 2013 11:58, David Booth wrote: > On 04/02/2013 05:02 PM, Alan Ruttenberg wrote: > >> On Tuesday, April 2, 2013, David Booth wrote: >> On 03/27/2013 10:56 PM, Pat Hayes wrote: >> On Mar 27, 2013, at 7:32 PM, Jim McCusker wrote: >> >> If only owl:sameAs were used

Re: owl:sameAs - Harmful to provenance?

On 04/02/2013 05:02 PM, Alan Ruttenberg wrote: On Tuesday, April 2, 2013, David Booth wrote: On 03/27/2013 10:56 PM, Pat Hayes wrote: On Mar 27, 2013, at 7:32 PM, Jim McCusker wrote: If only owl:sameAs were used correctly... Well, I agree that is a problem, but d

Re: owl:sameAs - Harmful to provenance?

On Tuesday, April 2, 2013, David Booth wrote: > On 03/27/2013 10:56 PM, Pat Hayes wrote: > >> On Mar 27, 2013, at 7:32 PM, Jim McCusker wrote: >> >>> If only owl:sameAs were used correctly... >>> >> >> Well, I agree that is a problem, but don't draw the conclusion that >> there is something wrong

Re: owl:sameAs - Harmful to provenance?

On 03/27/2013 10:56 PM, Pat Hayes wrote: On Mar 27, 2013, at 7:32 PM, Jim McCusker wrote: If only owl:sameAs were used correctly... Well, I agree that is a problem, but don't draw the conclusion that there is something wrong with sameAs, just because people keep using it wrong. Agreed. And

返: owl:sameAs - Harmful to provenance?

ith >> meta-information about that information. The meta-information is not about >> the thing. > > If only owl:sameAs were used correctly... > > One thing to note is that provenance is for more than data. The issues I > discuss in that presentation (and the following pa

Re: owl:sameAs - Harmful to provenance?

:SymmetricProperty" > The effect of A owl:sameAs B is, that A and B become two names for the same > thing, thus statements about A and B are merged and provenance information is > lost. After stating A skos:exactMatch B (and also A skos:closeMatch B, for > that matter) there are

Re: owl:sameAs - Harmful to provenance?

metricProperty" > > The effect of A owl:sameAs B is, that A and B become two names for the > same thing, thus statements about A and B are merged and provenance > information is lost. After stating A skos:exactMatch B (and also A > skos:closeMatch B, for that matter) there are

Re: owl:sameAs - Harmful to provenance?

are merged and provenance information is lost. After stating A skos:exactMatch B (and also A skos:closeMatch B, for that matter) there are still two things with statements about them coming from different sources. Thus, there is nothing wrong with the semantics of owl:sameAs, only in the way it i

Re: owl:sameAs - Harmful to provenance?

On Mar 27, 2013, at 7:56 PM, Pat Hayes wrote: > I guess your analogy to GOTO put my back up a little. I rather liked the GOTO/owl:sameAs presentation … and I am not sure that the problem can be explained away as modeling errors. To me it does seem that there is a case to answer … modeling is

Re: owl:sameAs - Harmful to provenance?

carefully considered before they are used directly. We selected that title to provoke discussion (it was an abstract submission), which it successfully did. > Well, I'm not (yet) sure what "entity provenance" means, but the main > point is that if you have some information ab

Re: owl:sameAs - Harmful to provenance?

ing wrong with sameAs, just because people keep using it wrong. I guess your analogy to GOTO put my back up a little. > > One thing to note is that provenance is for more than data. The issues I > discuss in that presentation (and the following papers) are more about entity > prov

Re: owl:sameAs - Harmful to provenance?

thing with meta-information about >> that information. The meta-information is not about the thing. >> > > If only owl:sameAs were used correctly... > One thing to note is that provenance is for more than data. The issues I discuss in that presentation (and the following p

Re: owl:sameAs - Harmful to provenance?

On Wed, Mar 27, 2013 at 8:30 PM, Jim McCusker wrote: > On Wed, Mar 27, 2013 at 8:26 PM, Pat Hayes wrote: > >> That "option" is already available, if you use owl:sameAs correctly (and >> do not confuse information about some thing with meta-information about >> that information. The meta-informat

Re: owl:sameAs - Harmful to provenance?

On Wed, Mar 27, 2013 at 8:26 PM, Pat Hayes wrote: > That "option" is already available, if you use owl:sameAs correctly (and > do not confuse information about some thing with meta-information about > that information. The meta-information is not about the thing. > If only owl:sameAs were used c

Re: owl:sameAs - Harmful to provenance?

On Mar 27, 2013, at 12:31 PM, Rafael Richards wrote: > This has been a very prolific thread, but did we discuss provenance? > > A slideshare on owl:sameAs - Harmful to Provenance is here: > > http://www.slideshare.net/jpmccusker/owlsameas-considered-harmful-to-provenance &g

Re: owl:sameAs - Harmful to provenance?

rties, such as prov:wasQuotedFrom and prov:wasAttributedTo, that are incredibly useful just by themselves. I use it as a core ontology partly because my view of biomedical entities ends up looking very much like provenance anyway, so it helps me keep things interoperable from the start. Jim On Wed, M

Re: owl:sameAs - Harmful to provenance?

down the road I will have to concern myself with provenance, but more in terms of the creation and dispersion of basic science knowledge than things directly impinging on medically related knowledge. Thanks for alerting me to PROV. - Bob On Wed, Mar 27, 2013 at 3:42 PM, Jim McCusker wrote: &

RE: owl:sameAs - Harmful to provenance?

It's also encouraging that w3c HCLS is focusing actively on the provenance discussion. We've found (and presented on) practical benefits from use of PROV-O and VoID. All the best, Bob From: Jim McCusker [mailto:james.mccus...@yale.edu] Sent: Wednesday, March 27, 2013 1

Re: owl:sameAs - Harmful to provenance?

Which is why PROV exists. Now we have a floor to work from. I've already integrated it into a number of projects. Jim On Wed, Mar 27, 2013 at 3:39 PM, Bob Futrelle wrote: > Provenance techniques/tools/systems are nowhere near what they could to be. > Each provenance system or &quo

Re: owl:sameAs - Harmful to provenance?

Provenance techniques/tools/systems are nowhere near what they could to be. Each provenance system or "standard" ends up being unique so the information is not inter-operative. One example among the many: http://openprovenance.org/ These days, I'm more focused on NLP than se

Re: owl:sameAs - Harmful to provenance?

The short answer: not anymore, if you use prov:alternateOf and prov:specializationOf instead. Jim On Wed, Mar 27, 2013 at 1:31 PM, Rafael Richards wrote: > This has been a very prolific thread, but did we discuss provenance? > > A slideshare on owl:sameAs - Harmful to Provenanc

Re: owl:sameAs - Harmful to provenance?

This has been a very prolific thread, but did we discuss provenance? A slideshare on owl:sameAs - Harmful to Provenance is here: http://www.slideshare.net/jpmccusker/owlsameas-considered-harmful-to-provenance Presentation Abstract: GOTO was once a standard operation in most computer

[LLD Announce Monday] Bio2RDF Release 2: Improved coverage, interoperability and provenance of Linked Data for the Life Sciences

[Information on joining the meeting is at the bottom of this message. -Scott] Title: Bio2RDF Release 2: Improved coverage, interoperability and provenance of Linked Data for the Life Sciences Abstract: Bio2RDF is an open source project that uses Semantic Web technologies to build and provide the

ProvBench: Provenance Benchmark Challenge at EDBT/ICDT 2013

** Apologies for cross-posting** ProvBench, Provenance Benchmark Challenge, co-located at BigProv'13 (The International Workshop on Managing and Querying Provenance Data at Scale) Final Call for Expressi

[CFP] BigPROV @EDBT 2013: Workshop on Managing and Querying Provenance Data at Scale

* Call for Papers * BIGProv'13: International Workshop on Managing and Querying Provenance Data at Scale http://sites.google.com/site/bigprov13/ inquiries: bigpro...@easychair.org Held in conjunction with EDBT/ICDT 2013: http://edbticdt2013.disi.unige.it/ *March 22nd, 2013, Genova,

NCBO Webinar: Yolanda Gil, June 20 - Semantic Workflows and Provenance-Aware Software

The next NCBO Webinar will be presented by Yolanda Gil from USC/ISI on "Semantic Workflows and Provenance-Aware Software" at 10:00am PDT, Wednesday, June 20. Below is information on how to join the online meeting via WebEx and accompanying teleconference. For the full schedule of the NC

Call for participation: The Third Semantic Web and Provenance Management (SWPM 2012) workshop

*** SWPM 2012: The Third International Workshop on the role of Semantic Web in Provenance Management *** http://sites.google.com/site/swpm2012/program Co-located with the 9th Extended Semantic Web Conference ESWC-2012 in Heraklion, Crete http://2012.eswc-conferences.org/ Date: The workshop

W3C Provenance Working Group Drafts -- ready for review

** Release of the W3C Provenance Working Group Primer, Ontology, and Data Model Working Drafts **  Hello, The Provenance Working Group is happy to announce that 5 working drafts available for review including a primer, ontology and data model. These drafts define a model for interchanging

[CFP] Call for participation: : SWPM 2012: The Third International Workshop on the role of Semantic Web in Provenance Management

/// Apologies for cross-posting Dear all, I am pleased to announce on behalf of the SWPM organizers that we are going to continue to explore the common ground between semantic web technologies and provenance information in this year's ESWC, to take place on 28th May, 2012 in Hera

Deadline extension: SWPM2012 workshop @ ESWC (Role of Semantic Web in Provenance Management)

* Call for Papers: SWPM2012 (Deadline Extended to 16th March 2012) * The Third International Workshop on the role of Semantic Web in Provenance Management website: http://sites.google.com/site/swpm2012/ e-mail: swpm2...@googlegroups.com Held in conjunction with the 9th

4th International Provenance and Annotation Workshop (IPAW'2012)

Apologies for cross-posting --- Call for Papers: 4th International Provenance and Annotation Workshop (IPAW'2012) June 19-21, 2012 - Santa Barbara, California Deadline March 21, 2012 http://ipaw2012.bren.ucsb.edu/ *Overview* "Provenance of

Re: The Provenance Spectrum....

Hello Michel, Latest work of the provenance wg is here - http://dvcs.w3.org/hg/prov/raw-file/tip/model/ProvenanceModel.html Where both the model of provenance and how provenance assertions can be created are graphically illustrated. My role in the prov wg is to make sure that there is a smooth

Re: The Provenance Spectrum....

As a testament to the growing recognition of provenance for (e-)science, i'm glad to see that the incubator group worked hard to think about the issues and record them. a good starting point: "provenance is often represented as metadata, but not all metadata is necessarily proven

Re: The Provenance Spectrum....

Hi Joanne and Scott, In the Provenance incubator we agreed on the following definition: Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing

The Provenance Spectrum....

Thank you Scott for suggestion that we move the discussion to the mailing list... and to include the provenance working group. What is provenance? Where do we draw the line in the definition? Our HCLSIG TMO discussion today was reminiscent of the 'what is an ontology discussion?'. A

Re: provenance questionnaire, v2

ts, but there are many useful datasets which are >> subscription only, or, for example, free to academia but subscription for >> industry. I think being able to have subsets of RDF in a combined repository >> which can be "unlocked" wi

Re: provenance questionnaire, v2

can be "unlocked" with a license would be useful, and it strikes me > this is a provenance / authorization thing? > > David > > > Dr. David J. Wild, djw...@indiana.edu, http://djwild.info > Assistant Professor of

Re: provenance questionnaire, v2

industry. I think being able to have subsets of RDF in a combined repository which can be "unlocked" with a license would be useful, and it strikes me this is a provenance / authorization thing? David Dr. David J. Wild, djw...@indiana

Re: provenance questionnaire, v2

On Tue, Sep 6, 2011 at 11:18 AM, Deus, Helena wrote: > I will forward you concerns to the provenance workgroup. Well, authorization is going to be a big thing in our EU project... various reasons for that, social, contractual, political. That's just the way it is. I can elaborate furthe

RE: provenance questionnaire, v2

hi all, i would think that an authorization trail would be very important (a quick search on the web for 'provenance authorization' came up with many hits so perhaps there is already one that can be incorporated). in the museum world, for art works that disappeared during world war

RE: provenance questionnaire, v2

Thanks Egon, The provenance wg has been briefly concerned with authorization, but nothing too concrete has been devised yet. I will forward you concerns to the provenance workgroup. Cheers, Lena -Original Message- From: Egon Willighagen [mailto:egon.willigha...@gmail.com] Sent: 06

Re: provenance questionnaire, v2

On Thu, Sep 1, 2011 at 11:42 PM, Deus, Helena wrote: > For those of you who haven’t answered and would like to give your 2c about > how provenance should be dealt with on the semantic web, here’s your chance! Authorization would probably not be considered provenance, but I was wondering

provenance questionnaire, v2

Dear all, Thank you to those of you who have answered our first provenance Implementation Stakeholder questionnaire, your feedback is very important. For those of you who haven't answered and would like to give your 2c about how provenance should be dealt with on the semantic web, h

Re: need help identifying communities to contact for W3C Provenance WG user survey

Stephan, sending to the W3C public semantic web mailing list so that you may get a broader input from the community at this stage and BAMBCT (Boston Area Molecular Biology and Computer Types). Be sure to add criteria and examples - so that people who are not familiar with the term provenance

Scientific Discourse Meeting, July 25, 2011: Ping Wang, Rensellear Polytechnic: A Semantically-Enabled Provenance-Aware Water Quality Portal

. Anita de Waard Disruptive Technologies Director, Elsevier Labs http://elsatglabs.com/labs/anita/ a.dewa...@elsevier.com Scientific Discourse Meeting, July 25, 2011 Agenda: 1. Talk Ping Wang 2. Ontologies status 3. AOB. Ping Wang, Rensellear Polytechnic: A Semantically-Enabled Provenance-Aware

survey about provenance

<> The W3C Provenance Working Group [1] is working on defining a standard for provenance. The group is conducting a survey [2] to identify and connect with potential implementation stakeholders and coordinate test case development and implementation activities. If you o

Re: [linkedlifew3cnote] Re: Linkset Provenance

Message- From: Mark Wilkinson [mailto:ma...@illuminae.com] Sent: 16 June 2011 16:18 To: linkedlifedatapracticesn...@googlegroups.com; Helena Deus Cc: Claus Stie Kallesøe; HCLS; Anja Jentzsch Subject: Re: [linkedlifew3cnote] Re: Linkset Provenance < "drugX" rdf:type myshema:dr

Re: [linkedlifew3cnote] Re: Linkset Provenance

On Thu, 16 Jun 2011 09:06:47 -0700, Helena Deus wrote: Great to hear from you. Always nice to hear from you too!! M

Re: [linkedlifew3cnote] Re: Linkset Provenance

On Thu, 16 Jun 2011 09:06:47 -0700, Helena Deus wrote: I thought the drugs we two individuals (instances of drugs). < :drugX rdf:type myshema:drug > Here you are saying X is "type drug", asserting that "myschema:drug" is an OWL Class. Therefore... < myschema:drug owl:sameAs

RE: [linkedlifew3cnote] Re: Linkset Provenance

: linkedlifedatapracticesn...@googlegroups.com; Helena Deus Cc: Claus Stie Kallesøe; HCLS; Anja Jentzsch Subject: Re: [linkedlifew3cnote] Re: Linkset Provenance > < "drugX" rdf:type myshema:drug > and then somewhere else state that < > myschema:drug owl:sameAs someother:drug >. I

Re: [linkedlifew3cnote] Re: Linkset Provenance

Hi Mark, Great to hear from you. What would you recommend instead? I thought the drugs we two individuals (instances of drugs). On Thu, Jun 16, 2011 at 4:18 PM, Mark Wilkinson wrote: > > < :drugX rdf:type myshema:drug > and then somewhere else state that >> < myschema:drug owl:sameAs someother

Re: [linkedlifew3cnote] Re: Linkset Provenance

Thanks lena, very helpful claus - Original meddelelse - > Hi Claus, all > > Lately I have been preferring the second option, for > provenance/attribution issues  - I want to be able to separate my list > of instances of a class from the list of instances defined somewhere

Re: [linkedlifew3cnote] Re: Linkset Provenance

< "drugX" rdf:type myshema:drug > and then somewhere else state that < myschema:drug owl:sameAs someother:drug >. I wouldn't advise this - it's an OWL Full construct. You can only use sameAs to merge two *individuals* in OWL DL. Mark -- Dr. Mark Wilkinson Assistant Professor, Medica

Re: [linkedlifew3cnote] Re: Linkset Provenance

Hi Claus, all Lately I have been preferring the second option, for provenance/attribution issues - I want to be able to separate my list of instances of a class from the list of instances defined somewhere else. A neat way to do that is to say that < "drugX" rdf:type myshema:dr

Announcement: First Public Release of the Open Provenance Model Vocabulary (OPMV)

Dear all, I am pleased to announce the first public release of the Open Provenance Model Vocabulary (OPMV; http://purl.org/net/opmv/ns#). OPMV is designed as a lightweight provenance vocabulary by implementing the provenance community model, the Open Provenance Model [1]. It is driven by the

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

uot; ; "Ravi Shankar" Sent: Wednesday, November 10, 2010 4:21 AM Subject: Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance Interesting question and one we've been discussing in other contexts. HGNC is only valid for human genes of course, and not

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

On Tue, Nov 9, 2010 at 4:45 PM, mdmiller wrote: > this i've seen as more a de facto best practice than anything for > identifying a sequence (but i'm not sure what you mean by a standard input > format). I meant: what are valid and/or (minimally) required ways to refer to a gene? Is it enough to

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

Interesting question and one we've been discussing in other contexts. HGNC is only valid for human genes of course, and not all species have this type of sign off on ids. I would use an Ensembl id, from there you can get other id cross references best Helen On 10/11/2010 10:24, Christoph Gra

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

> The DO is a OBO Foundry candidate, and there is an official OWL > release [1], so wouldn't that be the authoritative source for URIs? Of > course it's easy to replace the definition_citations, but wouldn't it > be much nicer if the user can just download two 'officially' released > OWL files and

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

ott Marshall" ; "HCLS" Sent: Tuesday, November 09, 2010 2:09 AM Subject: Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance On Mon, Nov 8, 2010 at 4:02 PM, mdmiller wrote: 2) Many 'things' are represented as strings (e.g. genes), which makes

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

On Mon, Nov 8, 2010 at 4:02 PM, mdmiller wrote: > 2) Many 'things' are represented as strings (e.g. genes), which makes > it often impossible to run a federated query against another endpoint. > Gene names might somewhat consistent for HUGO, but what about other > species? Also, just the simple va

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

On Mon, Nov 8, 2010 at 3:50 PM, Helen Parkinson wrote: > EFO only uses namespaces from a subset of ontologies, mostly those which are > either OBO foundry approved, > or in the process of this, or where is a lack of orthogonal ontologies. For > disease we have many terms from many different source

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

hi all, my comments in line, cheers, michael - Original Message - From: "M. Scott Marshall" To: "HCLS" Cc: "Christoph Grabmueller" Sent: Monday, November 08, 2010 7:41 AM Subject: [BioRDF] Comments from Christoph Grabmuller on BioRDF microar

Re: [BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

Hi a few comments on the EFO parts of this. best Helen Generally I like the data model, seems intuitive to me. Btw in the graph at http://biordfmicroarray.googlecode.com/hg/sparql_endpoint.html the edge 'experimentSet dct:isPartOfmicroarray_experiment' is missing. What I have so far is a si

[BioRDF] Comments from Christoph Grabmuller on BioRDF microarray provenance

[Forwarding Christoph's comments on the BioRDF Provenance article draft for discussion. Cheers, Scott] Hello Scott, I finally had a look at the provenance draft, a few points: 1) Why is provenance so important? Is the lab where the data came from so significant? Or should I under

Scripts and refresh rates for LODD data + Key Provenance for federation issues

couldn't find the answers by looking at http://esw.w3.org/HCLSIG/LODD/Data . -- [CC'ing a sampling of people interested in federation and provenance.] Linked Open Drug Data task force has made important biomedical contributi

Call for Participation: the Second SWPM Workshop @ISWC'10: Role of Semantic Web in Provenance Management

Call for Participation The Second International Workshop on Role of Semantic Web in Provenance Management (SWPM 2010) Co-located with ISWC&#x

Deadline extension - SWPM 2009: Semantic Web in Provenance Management @ ISWC

Deadline Extended for Role of Semantic Web in Provenance Management (SWPM'10) Wor

Re: RDF Provenance for microarray data

I agree Tom with the need to record the provenance that you can. That's why it's particularly useful that James Malone (CC'd) told us about the Software Ontology http://www.ebi.ac.uk/efo/swo that is being developed in the context of the Experimental Factor Ontology work at EBI, q

3rd CFP: : Int. Workshop on Role of Semantic Web in Provenance (SWPM 2010) at ISWC2010

=== The Third CALL FOR PAPERS - SWPM 2010 === The Second International Workshop on Role of Semantic Web in Provenance Management (SWPM 2010

2nd CFP: Int. Workshop on Role of Semantic Web in Provenance (SWPM 2010) at ISWC2010

== The Second CALL FOR PAPERS - SWPM 2010 == The Second International Workshop on Role of Semantic Web in Provenance

First CFP: 2nd Int. Workshop on Role of Semantic Web in Provenance (SWPM 2010) at ISWC2010

== CALL FOR PAPERS - SWPM 2010 == The Second International Workshop on Role of Semantic Web in Provenance Management (SWPM

  1   2   >