- From: Chalk, Stuart <schalk@unf.edu>
- Date: Tue, 20 Oct 2015 12:03:44 +0000
- To: Nico Schlömer <nico.schloemer@gmail.com>
- CC: "public-linked-json@w3.org" <public-linked-json@w3.org>
You can represent relationships to previous versions by adding references to the DC terms ‘hasVersion’ and ‘isVersionOf’ (or other definitions of these relationships) - defining:
finalPaper hasVersion previousVersion
previousVersion isVersionOf finalPaper
In the final version “http://www.example.com/paper1/finalPaper” you might have
{
“@context”:
{
...
“priorVersion” : {
“@id”: “http://dublincore.org/documents/dcmi-terms/#terms-hasVersion”,
“@type”: “@id”
}
…
},
…
“priorVersion”: [
“http://www.example.com/paper1/previousVersion1”,
“http://www.example.com/paper1/previousVersion2”,
“http://www.example.com/paper1/previousVersion3”,
...
]
}
And in each version, e.g. "http://www.example.com/paper1/previousVersion1"
{
“@context”:
{
...
“finalVersion” : {
“@id”: “http://dublincore.org/documents/dcmi-terms/#terms-isVersionOf”,
“@type”: “@id”
}
…
},
…
“finalVersion”: “http://www.example.com/paper1/finalPaper”,
…
}
Stuart
> On Oct 19, 2015, at 12:22 PM, Nico Schlömer <nico.schloemer@gmail.com> wrote:
>
> Hi everyone,
>
> A scientific article is typically published in several revisions,
> e.g., a bunch of revisions on a preprint server like arXiv [1] plus
> possibly a version somewhere on a publisher's website [2]. The
> versions will generally be perceived as "the same article", but differ
> a little bit here and there. I'd hesitate to refer to them as the same
> document.
>
> Is it possible to express this kind of relationship in JSON-LD? What
> would you recommend?
>
> Cheers,
> Nico
>
>
> [1] http://arxiv.org/abs/1105.2785
> [2] http://journals.aps.org/prb/abstract/10.1103/PhysRevB.84.012505
>
Received on Friday, 23 October 2015 16:18:16 UTC