From: Rebecca Kennison <[log in to unmask]>
Date: Sun, 12 Jan 2014 19:31:56 -0500

If the author puts the article into a repository, the repository
manager would take care of this element, as they do many other
metadata fields. Authors using this schema on their own Web site would
be less likely to do so, I agree.

Best,
Rebecca


On Sun, Jan 12, 2014 at 6:01 PM, LIBLICENSE <[log in to unmask]> wrote:
>
> From: Sally Morris <[log in to unmask]>
> Date: Fri, 10 Jan 2014 12:16:17 +0000
>
> I am not sure that many authors would do even that.  What do others think?
>
> And in any case, would all publishers be happy to upload the alternative
> metadata for the freely available version of an article?  I suspect some
> might not.
>
> Human nature may be the weakness in this proposal!
>
> Sally
>
>
> Sally Morris
> Email:  [log in to unmask]
>
> -----Original Message-----
>
> From: Dietrich Rordorf / MDPI <[log in to unmask]>
> Date: Thu, 9 Jan 2014 08:00:18 +0100
>
> Dear Sally,
>
> You are right. However, the Publisher could deposit the metadata into
> CrossRef. The author then just needs to upload his pre/postprint + doi
> number to the repository. The repository can then easily fetch the metadata
> from CrossRef. (The metadata sets in CrossRef can be easily and publicly
> accessed, see example below.)
>
> curl -D - -L -H "Accept: application/unixref+xml"
> "http://dx.doi.org/10.1126/science.1157784"
>
> (Replace "10.1126/science.1157784" with any doi number. Curl:
> http://curl.haxx.se/)
>
> Best,
> Dietrich
>
> On 09.01.2014 01:00, LIBLICENSE wrote:
> >
> > From: Sally Morris <[log in to unmask]> Date: Wed, 8 Jan
> > 2014 11:36:01 +0000
> >
> > Publishers could certainly add this type of metadata, but what about
> > author-deposited OA materials?  Do we really think authors are going
> > to do it?
> >
> > Sally
> >
> > Sally Morris Email:  [log in to unmask]
> >
> > -----Original Message-----
> >
> > From: Dietrich Rordorf / MDPI <[log in to unmask]> Date: Tue, 7 Jan
> > 2014 08:02:57 +0100
> >
> > Marking-up the license *conditions* as XML would definitely be more
> > useful. Something quite generic like:
> >
> > <license ref="{publisher_or_license_url}">
> >
> > <copyright> <plain>{plain_copyright_statement}</plain> <owner
> > type="[individual|corporation|...]></owner> <year>{year}</year>
> > <country>[ISO 3166-1 alpha2/3 code]</country> </copyright>
> >
> > <use_allowed> <access type="[free|paid|..]"
> > ref="{publisher_condition_url}"></access> <read type="[free|paid|..]"
> > ref="{publisher_condition_url}"></read> <quote type="[free|paid|..]"
> > ref="{publisher_condition_url}"></quote> <cite type="[free|paid|..]"
> > ref="{publisher_condition_url}"></cite> <mine type="[free|paid|..]"
> > ref="{publisher_condition_url}"></mine>
> > </use_allowed>
> >
> > <use_disallowed> <commercial type="[free|paid|..]"
> > ref="{publisher_condition_url}"></commercial> <derivatives
> > type="[free|paid|..]" ref="{publisher_condition_url}"></derivatives>
> >  ... </use_disallowed>
> >
> > </license>
> >
> > etc.
> >
> > Kind regards, Dietrich Rordorf