Hi,
Yes, for a dataset or an information artifact, this would be like a logical
inclusion in the end.
However, if you point to is not an information artifact, hashes don't work as
well, unfortunately :(
But then, I think we are diverging too much on this list!(apologies)
best,
Andrea
Il giorno
Andrea,
the "range of verifiability" extends so long as the linked resources
are also trustyuris. You could, of course, cache and hash those linked
assertions, for posterity.
m.
On Sun, Sep 21, 2014 at 2:42 PM, Andrea Splendiani
wrote:
> HI,
> having hashes as part of URIs is very very good, i
HI,
having hashes as part of URIs is very very good, ihmo, for datasets. They are
IDs by definition.
For other kinds of informations it depends.
If I get correctly your proposal, you use hashes that extend to all references
(e.g.: they hash the hash...).
I wouldn't consider version of references
Martynas,
The Cool URIs proposal does not address versioning (and neither does
most metadata vocabularies), unfortunately. There's no reason why you
can't create URIs to return information that is known about an object
under some condition (APIs do that all the time). The key is that the
URI per
Joachim,
I think your proposal is in conflict with core Linked Data principle:
Cool URIs Don't Change.
http://www.w3.org/TR/cooluris/#cooluris
Martynas
graphityhq.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 w
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
*To be removed from our mailing list, please respond to this message with
UNSUBSCRIBE in the subject line*
**
2nd INTERNATIONAL CONFERENCE ON STATISTICAL LANGUAGE AND SPEECH PROCESSING
SLSP 2014
Grenoble, France
O
13 matches
Mail list logo
