Re: properties for periodical/creative work

On Thu, Nov 13, 2014 at 9:31 AM, François-Xavier Pelegrin <
francois-xavier.pelegrin@issn.org> wrote:

>  Hello,
>
> The ISSN International Centre is currently working on the addition of
> schema.org mark-up to the ISSN bibliographic records published on
> http://road.issn.org (beta version).
>

Great! That's exciting news!


> I wonder if we should use the property http://schema.org/contentRating
> or https://schema.org/reviewRating   for journal indicators (e.g. SNIP,
> SJR , Impact Factor) ?
>

I would not use schema:contentRating, as that seems to be intended for
distinguishing content meant for mature audiences vs. children.

Do journal indicators have maximum and minimum levels that can be mapped to
schema:Rating's bestRating and worstRating properties? A quick peek at
http://www.journalmetrics.com/faq.php suggests "maybe", which would be
ideal (to help a consumer understand the relative rating of the journal).


> Additionnally, what  property could we use for the data related to the
> indexing/abstracting of a resource ? (e.g.: the International Journal of
> Philosophy is indexed/abstracted by Scopus, see also the MARC 21 field
> n°510: http://www.loc.gov/marc/bibliographic/bd510.html):
>
> https://schema.org/review   or an inverse property (which does not exist
> yet -) of https://schema.org/citation  ?
>
> Could someone advice ?
>

Hmm. The idea of using the inverse of schema:citation is interesting; in
RDFa you could use the @rev property to do just that. It certainly seems
more accurate than schema:review.

Another possible direction to explore could be schema.org Actions,
specifically something along the lines of site searchlinks:
https://developers.google.com/webmasters/richsnippets/sitelinkssearch


> In other respects, I would recommend that you create the property ISSN-L
> for periodicals (ISSN-L = linking ISSN, it is used for collocate the
> various medium versions of the same resource, see
> http://www.issn.org/understanding-the-issn/assignment-rules/the-issn-l-for-publications-on-multiple-media/
> ).
>

When we last talked about ISSN properties (thread here:
http://lists.w3.org/Archives/Public/public-schemabibex/2013Nov/0058.html)
we opted to start with just plain ISSN. So if we decide to propose ISSN-L
now, given that many sites don't display an ISSN-L and only specialists
will understand the difference, I would suggest that we at least make
schema:issnL or schema:issnl (schema.org doesn't do punctuation in property
names) a sub-property of schema:issn so that some understanding of the
relationship between the properties can be inferred by machines.

That said, I'm still not convinced that there's much value to
distinguishing an ISSN from an ISSN-L given that the mapping between the
two is one of the simplest machine-automated processes possible ("I have an
ISSN--if it matches the ISSN-L in this table, then it's an ISSN-L and I
know it's linked to all of these other ISSNs; otherwise, it's an ISSN and I
can look up the ISSN-L that then gives me the links to all the other
ISSNs.")