ersion and its
actual current version to claim to be the current version. :). By
adding the has*Version relations we found a way to also be specific
about that "officialness".
--
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
http://soiland-reyes.com/stian/work/ http://orcid.org/-0001-9842-9718
anding conceptual thing (like a "version number") rather than
an equivalent snapshot of the resource.
--
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
http://soiland-reyes.com/stian/work/ http://orcid.org/-0001-9842-9718
d should/could anyway be the same of the last version, no?
>
> best,
> Andrea
>
> On Mon, Sep 22, 2014 at 1:04 PM, Stian Soiland-Reyes
> wrote:
>>
>> We have in PAV 2.3 also added pav:hasCurrentVersion which is the easy
>> way to link from an unve
tements)
>>>> that return what is known for http://example/P04637 at a given time.
>>>>
>>>> Note that http://example/P04637/V2 doesn't appear in results (except in
>>>> predicates linking different versions, like "replaces")
>>>>
>>>>
>>>> Basically I never have an assertion as:
>>>>
>>>> http://example/P04637 hasVersion 2, but version is only used to filter
>>>> which pack of information is relevant. So if I mix results from different
>>>> versions (e.g. quads) I can filter what is relevant and where to me.
>>>>
>>>>
>>>> Is this a common way of doing things ?
>>>>
>>>> If not, have you thought about it and if you took alternatives, why ?
>>>>
>>>>
>>>> best,
>>>>
>>>> Andrea
>>>
>>>
>>
>
--
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
http://soiland-reyes.com/stian/work/ http://orcid.org/-0001-9842-9718
> and the file
> gdac.broadinstitute.org_STAD.Merge_mirnaseq__illuminaga_mirnaseq__bcgsc_ca__Level_3__miR_gene_expression__data.Level_3.2014071500.0.0.tar.gz
> <http://gdac.broadinstitute.org/runs/stddata__2014_07_15/data/STAD/20140715/gdac.broadinstitute.org_STAD.Merge_mirnaseq__illuminaga_mirnaseq__bcgsc_ca__Level_3__miR_g
://purl.org/pav/
OWL import 2.3:
http://purl.org/pav/2.3
Further documentation:
http://purl.org/pav/2.3/html
Cite as:
Paolo Ciccarese, Stian Soiland-Reyes, Khalid Belhajjame, Alasdair JG
Gray, Carole Goble, Tim Clark (2013): PAV ontology: provenance,
authoring and versioning. Journal of biomedical
re are multiple sources.
On 11 Aug 2014 15:53, "Gray, Alasdair J G" wrote:
> Hi Stian,
>
> On 5 Aug 2014, at 13:37, Stian Soiland-Reyes <
> soiland-re...@cs.manchester.ac.uk> wrote:
>
> Just some inputs:
>
>
> PROV defines prov:wasDerivedFrom which in b
iew of dataset description level metadata profiles
> and their relationships': reference not resolved, image doesn't show
>
> ยท Figure 2: 'Improve diagram. Multiple appearance of
> concepts/description levels unclear.': reference not resolved, image doesn'
nwhile keeping precise distinctions between
concepts such as authoring/creating and importing/retrieving. In our
blog post [2] we also show how PAV can be use concurrently with other
PROV extensions, and how PROV tools can be used for interoperability
such as visualization.
*) This announcement is se
is no registration fee but RSVP (online) is required. RSVP for a
rollout near you using one of the links above.
For more information and individual agendas, see:
<http://www.openannotation.org/RolloutInfo.html>
--
On behalf of Open Annotation Community Group
Stian Soiland-Reyes, myGrid tea
sed this side of Christmas, we just need to do a few tweaks with
imports. For a preview, see:
http://www.essepuntato.it/lode/http://pav-ontology.googlecode.com/svn/branches/2.1/pav.owl
Namespaces and imports should be the same <http://purl.org/pav/>,
unless you explicitly imported the previ
11 matches
Mail list logo
