Hi Carole,
I participate in the data citation implementation group @ force11,
along with Tim Clark and others in this community.
https://www.force11.org/datacitationimplementation
does a specific aspect come to mind?
m.
On Mon, Sep 22, 2014 at 3:29 AM, Carole Goble
wrote:
> Hi all.
>
> At t
Hi,
I think hasVersion can be vague. In my case it has the specific meaning of
"time-snapshot" from a "master" information resource. So I can have
hasVersion and versionOf as inverse (not that I have committed to this and
I may adopt a more relaxed vocabulary, but I could).
Closed vs Open World: yo
On 22 September 2014 14:19, Andrea Splendiani
wrote:
> ok, so it seems our representations are pretty much aligned, except for the
> "http://example.com"; I don't say anything but simply redirect to the current
> versions.
I think that's fine as long as it's not in conflict with say the HTML
repr
Hi,
ok, so it seems our representations are pretty much aligned, except for the
"http://example.com"; I don't say anything but simply redirect to the
current versions. Each version page state things like "this is a version of
http://example.com, previousVersion... and so on. Latest version is the
o
On 22 September 2014 12:59, Andrea Splendiani
wrote:
> Ho,
> a related question:
> hasPreviousVersion: what does it have for domain/range ?
> I would use this relations as a predicate on versions only. Leaving
> relations among versions independent from the versioned object.
Note that there is no
aphityhq.com
>> >>
>> >> On Fri, Sep 19, 2014 at 7:14 PM, Joachim Baran
>> >> wrote:
>> >>> Hi!
>> >>>
>> >>> I would reorder the URI as "http://eample/V2/P1234";. That way you
>> >>> make it
>> >
; I would reorder the URI as "http://eample/V2/P1234";. That way you
> make it
> >>> more explicit that you are talking about data set releases, each of
> which is
> >>> defined by its own URI prefix. That way you can have two P1234 residing
> >>>
tely different.
>>>
>>> Should the version always be part of an URI? I would say yes -- despite
>>> seeing your argumentation about the temporal interpretation of URIs that you
>>> gave.
>>>
>>> Kim
>>>
>>> On 19 September 2
Hi all.
At the research data alliance meeting. The data citation wg lead by Andreas
Rauber is all about dynamic Datasets. They have some pilots
Michel- are you connected with that?
Carole
Sent from my iPhone by
Professor Carole Goble
The University of Manchester
UK
> On 21 Sep 2014, at 22:
d reorder the URI as "http://eample/V2/P1234";. That way you make it
>>>>> more explicit that you are talking about data set releases, each of which
>>>>> is
>>>>> defined by its own URI prefix. That way you can have two P1234 residing
>>>>
V2/P1234";. That way you make it
>>>> more explicit that you are talking about data set releases, each of which
>>>> is
>>>> defined by its own URI prefix. That way you can have two P1234 residing
>>>> side-by-side even though they might be completel
ix. That way you can have two P1234 residing
>>> side-by-side even though they might be completely different.
>>>
>>> Should the version always be part of an URI? I would say yes -- despite
>>> seeing your argumentation about the temporal interpretation of URIs
tely different.
>>
>> Should the version always be part of an URI? I would say yes -- despite
>> seeing your argumentation about the temporal interpretation of URIs that you
>> gave.
>>
>> Kim
>>
>> On 19 September 2014 08:38, Andrea Splendiani
>>
ways be part of an URI? I would say yes -- despite
> seeing your argumentation about the temporal interpretation of URIs that you
> gave.
>
> Kim
>
> On 19 September 2014 08:38, Andrea Splendiani
> wrote:
>>
>> Hi,
>>
>> I'm posting here a questio
Hi,
I knows how nanopubs work.
Let's say the closer thing I can find to what I need is git, just with a
different id policy.
best,
Andrea
Il giorno 21/set/2014, alle ore 22:00, Michel Dumontier
ha scritto:
> Hi Andrea,
> The nanopublication schema is a general mechanism to associate some
> pr
Hi Andrea,
The nanopublication schema is a general mechanism to associate some
provenance with one or more assertions, and to keep track of who put
this information together in a convenient package. There's nothing
that prevents you from sticking a whole ontology in the assertion
graph, and then p
Thanks Kerstin,
I am familiar with the CDISC RDF as we aim to reuse it in eTRIKS (where
CDISC and we are a part of) and see how to best linked it to the
LinkedISA work. This will also very much useful for the CEDAR centre.
More off list to avoid spanning all.
Thanks,
Susanna
On 21/09/2014 13:
Hi and Many Thanks Susanna for your email
The coverage for CRL was metadata describing prospective clinical data
standards, both public such as CDISC and internal such as raw data
standards for a specific clinical project, as well as descriptions of
retrospectiive datasets.The projejct was stopped
Hi Kerstin,
/(sl//ightly diverging from the subject of this tread)/
I am not sure which data standards will you cover in the registry and
wonder if there is a opportunity for collaboration. You may be familiar
with http://www.biosharing.org/ where registering data/metadata
reporting standards i
Hi Andrea,
in an earlier attempt to design and launch a Metadata Registry for clinical
trial data, called Clinical Reference Library1 ). To capture and manage
descriptions of versions of clinical trial data standards, and of variants
of actual clinical trial datasets, we applied the software patter
Hi,
I may re-use some bits of it, but overall I am dealing with quite a different
thing.
I don't have "publications", I have evolving information sets.
Provenance/evidence and the like are there, but not so fine-grained (e.g.: I
may have the whole ontology with the same provenance/evidence, not
+1
On 19 September 2014 20:07:52 CEST, Michel Dumontier
wrote:
>Hi,
> I suggest nanopublications to track versioning for assertions
> http://www.nanopub.org/guidelines/
>
>m.
>
>On Fri, Sep 19, 2014 at 9:58 AM, Joachim Baran
> wrote:
>> Hi!
>>
>> On 19 September 2014 09:45, Andrea Splendiani
>
Hi,
I suggest nanopublications to track versioning for assertions
http://www.nanopub.org/guidelines/
m.
On Fri, Sep 19, 2014 at 9:58 AM, Joachim Baran wrote:
> Hi!
>
> On 19 September 2014 09:45, Andrea Splendiani
> wrote:
>>
>> When a concept change meaning, it changes id ;)
>
> Aha! I thi
Hi!
On 19 September 2014 09:45, Andrea Splendiani
wrote:
> When a concept change meaning, it changes id ;)
>
Aha! I think it might not always change ID! ;)
Best wishes,
Kim
residing side-by-side even though they might be completely different.
>>>
>>> Should the version always be part of an URI? I would say yes --
>>> despite seeing your argumentation about the temporal interpretation of URIs
>>> that you gave.
>>>
>>
gt;>
>> Should the version always be part of an URI? I would say yes -- despite
>> seeing your argumentation about the temporal interpretation of URIs that
>> you gave.
>>
>> Kim
>>
>> On 19 September 2014 08:38, Andrea Splendiani > > wrote:
&g
letely different.
>
> Should the version always be part of an URI? I would say yes -- despite
> seeing your argumentation about the temporal interpretation of URIs that
> you gave.
>
> Kim
>
> On 19 September 2014 08:38, Andrea Splendiani
> wrote:
>
>> Hi,
>
different.
Should the version always be part of an URI? I would say yes -- despite
seeing your argumentation about the temporal interpretation of URIs that
you gave.
Kim
On 19 September 2014 08:38, Andrea Splendiani
wrote:
> Hi,
>
> I'm posting here a question I have posted in some ot
Hi,
I'm posting here a question I have posted in some other forums.
How do you go about versioning ?
I tend to think at the URI as pointing to the endurant, and this
leaves to the "version" the meaning of "what was known/true about an
entity at a given time". The latter
29 matches
Mail list logo
