Name: articleAbstractFormat: TextDescription: The abstract or summary of the article.Name: volumeFormat: TextDescription: The print volume that this article was published in.Name: issueFormat: TextDescription: The print issue that this article was published in.Name: pagesFormat: TextDescription: The printed page range for this article.Name: locatorFormat: TextDescription: A description (often numeric) that locates this article within its publication.Name: doiFormat: TextDescription: The digital object identifier (DOI) used to uniquely identify an objectName: pmidFormat: TextDescription: The PMID (PubMed identifier or PubMed unique identifier) assigned to this article's PubMed record.Name: publicationFormat: TextDescription: The full name of the journal or publication the article was published in.Name: publicationAbbreviationFormat: TextDescription: The PubMed or other scholarly abbreviation of the journal or publication this article was published in.Name: issnFormat: TextDescription: The International Standard Serial Number used to identify the print edition.Name: eissnFormat: TextDescription: The International Standard Serial Number used to identify the electronic edition.Name: ownerFormat: TextDescription: The copyright holder for this article.Name: rightsFormat: TextDescription: The license status for this article.Name: citesFormat: ScholarlyArticle, Book, or CreativeWorkDescription: A reference that this article cites.
Thanks so much for the feedback. I did include referenced material - I
believe I called it "cites" or "cites". Take a look and see if that
fits your needs.
thanks!
Rachel
This is useful.
I think it would be good to align this with he work that has already
been done in the Bibliographic ontology - why not just use their terms
as documented? Looks like most of what you have presented here is
already pretty much aligned with that work already
(http://bibotools.googlecode.com/svn/bibo-ontology/trunk/doc/index.html).
As I understand it BIBO is more or less aligned with the way citation
data is handled in Zotero and Mendeley.
> Name: articleAbstract
> Format: Text
> Description: The abstract or summary of the article.
Why not description or abstract? This could then be used for multiple types.
> Name: rights
> Format: Text
> Description: The license status for this article.
This must have been covered somewhere else in schema.org I am assuming.
> Name: cites
> Format: ScholarlyArticle, Book, or CreativeWork
> Description: A reference that this article cites.
Yes, just working through the use case I am working on looking at
embedded citation data the work would be of type ScholarlyArticle and
the cites property could refer to another ScholarlyArticle item.
--
-------------------------------
Peter Sefton +61410326955 p...@ptsefton.com http://ptsefton.com
Gmail, Twitter & Skype name: ptsefton
This will not harm the parsing by the big three ones and provide the data for new applications.
Plus, it may become relevance factors for your page for specific queries.
See here for examples:
http://wiki.goodrelations-vocabulary.org/Microdata
and
http://www.slideshare.net/mhepp/extending-schemaorg-with-goodrelations-and-wwwproductontologyorg
Martin
Martin
--------------------------------------------------------
martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen
e-mail: he...@ebusiness-unibw.org
phone: +49-(0)89-6004-4217
fax: +49-(0)89-6004-4620
www: http://www.unibw.de/ebusiness/ (group)
http://www.heppnetz.de/ (personal)
skype: mfhepp
twitter: mfhepp
It wasn't until this past Wednesday when some of the rNews properties
were included in Schema.org (or at least announced to be, during the
Schema.org Workshop). Now there are, as a part of CreativeWork:
* copyrightHolder
* copyrightYear
* copyrightNotice (though, as referenced elsewhere on this list, this
one isn't showing up in CreativeWork, but it is showing up on /Painting,
oddly).
"rights" seems to have some overlap with those above terms, but it would
be wonderful, from a licensing perspective, to have a property that
doesn't take free text, but instead a URL to a license. Just to give it
a name to refer to: something like "copyrightLicenseUrl"
That may meet the needs of many community members, including HighWire
Press, which needs to make reference to multiple types of copyright
licenses depending on the article.
As an aside: Should this discussion move to the newly created
public-vocab mailing list[0] as per the new Web Schemas Task Force[1]
that was announced[2]?
Best,
Greg
[0] http://lists.w3.org/Archives/Public/public-vocabs/
[1] http://www.w3.org/2001/sw/interest/webschema.html
[2] http://www.w3.org/QA/2011/09/proposing_two_new_sw_interest.html
--
| Greg Grossmeier |
| http://grossmeier.net |
copyrightLicenseUrl is clearly needed on CreativeWork to obtain same
functionality currently available in rel="license" (which works as a
microformat and RDFa).
I'd approach a LicensingRights type with caution. Lots of things can
be relevant to copyright status and licensing. A dedicated type could
easily become a poorly thought out "rights expression language", for
which there isn't much evidence of usefulness of in the wild (i.e.,
deployed on the web). CC has been rather successful in just getting
people to point to a specific license URL, which is both very simple
and extensible.
Mike