W3C home > Mailing lists > Public > public-vocabs@w3.org > April 2014

Re: Citation markup with Periodical proposal

From: Wes Turner <wes.turner@gmail.com>
Date: Sun, 13 Apr 2014 08:05:48 -0500
Message-ID: <CACfEFw_kuJaNT=70NhKNYDcGg5b4BFnvNGBK9WckrNVEqZ-X7g@mail.gmail.com>
To: kcoyle@kcoyle.net
Cc: "<public-vocabs@w3.org>" <public-vocabs@w3.org>
I describe a use case for structured data citations of works and data
in service of validating reproducible science in [4]; which could be
dramatically enhanced by RDFa (and/or Microdata) citation
discoverability. Most of this EmailMessage is a summarization of [4].

Clearly, COinS:

* has industry support
* is not RDF

One gap between COinS and (schema.org) RDFa mentioned in [4] was
first/middle/last to schema:name.
FML is clearly a western surname pattern.
I am not clear on Unicode collation policies for various CSLs.

Zotero:

* utilizes Citeproc-js to generate textual bibliographies
  (in RTF, TXT, and HTML)
  from CSL JSON
  (which cannot then be read back into Zotero RDF)
* can export a folder of citations as COinS, Zotero RDF, and a number
of other formats.
* also has extensions for various office suites.

A JSON-LD context for CSL JSON would be relatively simple; but:

* That's not HTML
* That's not Schema.org

RDFa @content [5] could help to preserve more complete bibliographic
data while still 'validating' as a particular CSL style (such as MLA).

Thanks for the CITO pointer! Recently [6] I learned of Hypothes.is
[7], an application built upon OpenAnnotation RDF [8] :

> [...] an interoperable framework for creating associations between related resources, annotations, using a methodology that conforms to the Architecture of the World Wide Web. Open Annotations can easily be shared between platforms, with sufficient richness of expression to satisfy complex requirements while remaining simple enough to also allow for the most common use cases, such as attaching a piece of text to a single web resource.
>
> An Annotation is considered to be a set of connected resources, typically including a body and target, where the body is somehow about the target. The full model supports additional functionality, enabling semantic annotations, embedding content, selecting segments of resources, choosing the appropriate representation of a resource and providing styling hints for consuming clients.

OpenAnnotation builds upon dcterms, dctypes, foat, prov, and a number
of other popular schemas. [9]

I've done a bit of research on sharing statistical datasets with RDF
[10][11]. It's not clear to me how to indicate that a
schema:CreativeWork references a schema:Dataset or schema:Catalog.

Thanks again!

[4] https://forums.zotero.org/discussion/35992/export-to-schemaorg-rdfa-andor-microdata/
[5] http://www.w3.org/TR/rdfa-core/#object-resolution
[6] http://www.reddit.com/r/semanticweb/comments/20nvj6/open_annotation_data_model_w3c_community_draft_rdf/
[7] http://www.openannotation.org/spec/core/
[8] http://hypothes.is/what-is-it/
[9] http://www.openannotation.org/spec/core/#Namespaces
[10] https://github.com/pydata/pandas/issues/3402
[11] http://www.reddit.com/r/semanticweb/comments/21w5cr/rfc_reproducible_statistics_and_linked_data/

On 4/13/14, Karen Coyle <kcoyle@kcoyle.net> wrote:
>
>
> On 4/12/14, 11:01 AM, Wes Turner wrote:
>> Thanks!
>>
>> This seems especially helpful and in support of "Joint Declaration of
>> Data Citation Principles" (Human Understandable and
>> Machine-Actionable) [1]
>
> Wes,
>
> Good addition to the conversation. Since this proposal is based around
> periodicals and multi-volume works, it would probably need to be
> separate from it. (Note that there are other things that are cited, such
> as personal communications, that aren't yet covered in schema.org.) We'd
> want to think about how to indicate the data types, and I presume that
> someone has such a list. I know the NISO [1] is intending to work on
> rules for citing "observed" data. That will include things like data
> gathering techniques, fields, format, versioning, subsets, etc. (It can
> get quite complex). It remains to be seen if/when such a metadata format
> will come into use.
>
> There is also the Semantic Publishing and Referencing (SPAR) work that
> has an interesting set of citation types. [2] In that regard,
> CreativeWork has /citation that creates a non-specific relationship
> between the citation and the article ("is cited") whereas CiTO gives the
> specific reason for the citation (e.g. the motivation for the citation,
> "in suport of" "refuting" etc.). I would consider that to be a property
> of the citation statement and not the article description, and I'm not
> sure how/where it would fit into schema.org. But if there were citation
> types, then "supporting data" would make sense as a type, and more
> specific information may be available on the nature of the data set.
>
>
>>
>> I wonder whether this schmema.org microdata encoding of MLA citation
>> style would qualify as a new CSL citation style. [2][3]
>
> This looks like an excellent place to put examples.
>
>
>>
>> Microdata and/or RDFa output templates for Zotero would be neat. [4]
>
> The discussion there is interesting, and brings up some of the problems
> in going from citations to more detailed mark-up. However, they do
> mention COinS [3] (Context Object in Spans) which is already a citation
> markup in html and a Zotero export form. It may be a good source of
> information for a JSON-LD version of the citation, but adding schema
> markup to it would undoubtedly break all of the software that makes use
> of the COinS citations.
>
> Here's a quick COinS example:
> <span
>     class="Z3988"
>
> title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.genre=article&amp;rft.atitle=Managing+Sameness&amp;rft.title=Journal+of+Academic+Librarianship&amp;rft.stitle=jacalib&amp;rft.issn=0099-1333&amp;rft.date=2008-09&amp;rft.volume=34&amp;rft.issue=5&amp;rft.spage=452&amp;rft.epage=453&amp;rft.aulast=Coyle&amp;rft.aufirst=Karen&amp;rft.au=Karen+Coyle&amp;rft_id=info:doi/doi%3A10.1016%2Fj.acalib.2008.07.012"></span>
>
> In my own bibliographies, I'm planning on leaving these as they are, and
> will test to see if adding schema.org confusing the COinS readers.
>
> But, this also brings to mind that there used to be a COinS generator -
> where you filled in a form and it spit out the appropriate COinS (I
> believe it no longer exists). For bibliographic citations and for
> bibliographic data in certain field-delimited formats (BibTex, EndNote),
> it mibht be useful to provide an input/output service.
>
> kc
>
> [1] http://www.niso.org/topics/tl/researchdata/
> [2]
> http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/cito
> [3] http://ocoins.info/
>
>
>>
>> [1] http://www.force11.org/datacitation
>> [2] http://citationstyles.org/styles/style-repository/
>> [3] https://www.zotero.org/styles
>> [4]
>> https://forums.zotero.org/discussion/35992/export-to-schemaorg-rdfa-andor-microdata/
>> :
>>
>>> How would I go about adding HTML + RDFa [1] and/or HTML + Microdata [2]
>>> export templates with Schema.org classes and properties to Zotero?
>>>
>>> References
>>>
>>> [1] http://www.w3.org/TR/xhtml-rdfa-primer/
>>> [2] http://www.w3.org/TR/microdata/
>>> [3] https://en.wikipedia.org/wiki/Schema.org
>>> [4] http://schema.org/docs/full.html
>>> [5] http://lists.w3.org/Archives/Public/public-vocabs/2014Apr/0104.html
>>
>>
>>
>> On 4/11/14, Wallis,Richard <Richard.Wallis@oclc.org> wrote:
>>> Thanks Karen.
>>>
>>> When this gets adopted we can add a couple of examples to the
>>> SchemaBibex
>>> Recipes and
>>> Guidelines<http://www.w3.org/community/schemabibex/wiki/Recipes_and_Guidelines>
>>> section.  I may defer for assistance at that time to someone with a
>>> greater
>>> insight into citation styles than I have ;-)
>>>
>>>
>>> ~Richard
>>>
>>> On 11 Apr 2014, at 02:57, Karen Coyle
>>> <kcoyle@kcoyle.net<mailto:kcoyle@kcoyle.net>> wrote:
>>>
>>> Thanks, Richard. I did a modification of the markup with the date
>>> following
>>> the author's name (which is the APA, Turabian and Chicago style). The
>>> turtle
>>> is below. Because of the position of the date, the publication issue is
>>> invoked twice. If that's not a problem, then I'd suggest adding one of
>>> those
>>> formats as well to our extended "how to use" document.
>>>
>>> @prefix rdfa: <http://www.w3.org/ns/rdfa#> .
>>> @prefix schema: <http://schema.org/> .
>>> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
>>>
>>> <http://rdfa.info/play/>
>>>    rdfa:usesVocabulary schema: .
>>> _:1
>>>    rdf:type schema:ScholarlyArticle;
>>>    schema:author "Carlyle, Allyson.";
>>>    schema:isPartOf _:2;
>>>    schema:isPartOf _:3;
>>>    schema:isPartOf _:4;
>>>    schema:isPartOf _:5;
>>>    schema:name """Understanding FRBR as a Conceptual Model: FRBR
>>>     and the Bibliographic Universe""";
>>>    schema:pageStart "264";
>>>    schema:pageEnd "273";
>>>    schema:sameAs <http://dx.doi.org/10.1080/01639374.2012.682254> .
>>> _:2
>>>    rdf:type schema:PublicationIssue;
>>>    schema:datePublished "2006" .
>>> _:3
>>>    rdf:type schema:Periodical;
>>>    schema:name "Library Resources and Technical Services" .
>>> _:4
>>>    rdf:type schema:PublicationVolume;
>>>    schema:volumeNumber "50" .
>>> _:5
>>>    rdf:type schema:PublicationIssue;
>>>    schema:issueNumber "4" .
>>>
>>> kc
>>>
>>>
>>> On 4/10/14, 11:58 PM, Wallis,Richard wrote:
>>> An example for “/An article citation in MLA format, using a 'flat'
>>> approach that simplifies markup by not specifying an explicit
>>> relationship between the periodical, volume, and issue/” has now been
>>> added to the proposal document here
>>> <https://www.w3.org/wiki/WebSchemas/Periodicals,_Articles_and_Multi-volume_Works#Example_3_-_An_article_citation_in_MLA_format.2C_using_a_.27flat.27_markup_approach>.
>>>
>>>
>>> ~Richard
>>>
>>> On 9 Apr 2014, at 14:50, Wallis,Richard
>>> <Richard.Wallis@oclc.org<mailto:Richard.Wallis@oclc.org>
>>> <mailto:Richard.Wallis@oclc.org>> wrote:
>>>
>>> Coming out of a day of wall-2-wall meetings to find this list has made
>>> the points I was going to make and formed a general consensus is great!
>>>
>>> So all I can add is, support to Dan’s earlier comment that the
>>> SchemaBibex "/proposal slants toward hierarchical markup/” yet "/At
>>> the same time, we can also support quite flat markup/" - “ /..the
>>> proposal fills a significant gap in the schema.org<http://schema.org>
>>> <http://schema.org/> vocabulary./”
>>>
>>> Plus I acknowledge that the examples in the proposal are lacking one
>>> that demonstrates this flat approach.
>>>
>>> I will work with Dan to get such an example added to the proposal and
>>> also take this into account when we add to the SchemaBibEx Recipes and
>>> Guidelines
>>> <https://www.w3.org/community/schemabibex/wiki/Recipes_and_Guidelines>
>>> section,
>>> once it has been adopted
>>>
>>> Thanks to Karen for raising this and to all who contributed.
>>>
>>> ~Richard
>>>
>>> On 9 Apr 2014, at 14:14, Dan Scott
>>> <dan@coffeecode.net<mailto:dan@coffeecode.net>
>>> <mailto:dan@coffeecode.net>> wrote:
>>>
>>> On Wed, Apr 09, 2014 at 07:48:56PM +0200, Karen Coyle wrote:
>>> Thanks, Niklas and Dan and Adrian.
>>>
>>> Niklas, yours is a successful version of something that I tried
>>> unsuccessfully - nesting all of the periodical "parts" in between
>>> article properties. The turtle makes sense to me, even though the
>>> RDFa is hard to grasp (but then, I'm not a machine).
>>>
>>> Dan, I couldn't turtle-ize yours, and the rich snippet tool appears
>>> to be flaky and wouldn't spit out the pages section. It may be
>>> equivalent to Niklas' - I have no idea. Sorry.
>>>
>>> My fault: I'm much better at RDFa than I am at microdata; I should have
>>> prefixed http://schema.org/ to the PublicationVolume / PublicationIssue
>>> types in my microdata example. At least that works as I meant it to in
>>> http://linter.structured-data.org
>>> <http://linter.structured-data.org/> and
>>> http://rdf.greggkellogg.net/distiller (and by the way, Gregg, you rock
>>> for providing both of those services!)
>>>
>>> In any case, the core difference between Niklas's and my example is that
>>> I did not include any nesting, because I thought flat was what you were
>>> asking for. And yes, the Rich Snippet Tool is well-known for dropping
>>> properties that it doesn't recognize (it complains about isPartOf and
>>> presumably can't be bothered to complain about pageStart / pageEnd).
>>>
>>> Let's get this proposal adopted and put the Rich Snippet Tool to work!
>>>
>>>
>>>
>>>
>>> --
>>> Karen Coyle
>>> kcoyle@kcoyle.net<mailto:kcoyle@kcoyle.net> http://kcoyle.net
>>> m: 1-510-435-8234
>>> skype: kcoylenet
>>>
>>>
>>>
>>
>>
>
> --
> Karen Coyle
> kcoyle@kcoyle.net http://kcoyle.net
> m: 1-510-435-8234
> skype: kcoylenet
>


-- 
-- 
Wes Turner
Received on Sunday, 13 April 2014 13:06:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:39 UTC