Add publications property

[acka47]

We would like to have a property to link a Person, Event, Action, Organization (maybe just schema:Thing should be used as "domain") to a list of publications published by a person/organization or in the context of an event or action.

(This property would be similar to but more general than foaf:publications.)

Example use case:

The OER worldmap (GitHub) started collecting information on organizations, persons, events and projects (actions) in the context of Open Educational Resources (OER). It is making heavy use of schema.org (see e.g. the embedded JSON-LD on this page. I am currently adding the OER Africa project and would like to add a link to their publications page e.g. like this (snippet, the property in question being in the last line):

{
   "name" : [
      {
         "@value" : "OER Africa",
         "@language" : "en"
      }
   ],
   "@type" : "Action",
   "url" : "http://www.oerafrica.org",
   "startTime" : "2008",
   "publications": "http://www.oerafrica.org/about-us/our-resources-and-publications",
}

We will also need this when linking a personal profile to a publications list in the future.

[RichardWallis]

Just checking your description as this sounds like a conflation of several requirements.

Firstly: From the Person/Organization point of view, are you looking for the inverse of the created, author, contributor, etc. properties from CreativeWork that [if you were responsible for the markup] you would have defined for each publication?

Secondly: Looking at Event. Are you looking for a property, similar to workPerformed, that would reference workPresented, or workProduced, or productProduced, or even thingProduced?

Also wondering at your use of Action, to define the project. The OER Africa seems more Organization-like than Action-like to me.

~Richard

[RichardWallis]

Further thinking about this, and if my first Person/Organization understanding is correct, a property of 'created', or 'produced' with a range of Thing and a domainIncludes of Person and Organization would fit the requirement.

This would raise a couple of issues such as:

• Inverse properties not normally being encouraged - however in the case of publications and other things, described elsewhere and having no direct connection to the person/organization being described, I suggest this might be acceptable.
• For Organzation there maybe conflicts with Product style things and requirements to describe things that an organization produces, manufactures, or potentially produces as well as what the have produced.

A similar pattern may then work for Event.

~Richard

[acka47]

@RichardWallis You are right that the use cases might better be covered by more than one property but I am not yet sure about this.

From the Person/Organization point of view, are you looking for the inverse of the created, author, contributor, etc. properties from CreativeWork that [if you were responsible for the markup] you would have defined for each publication?

This definitely holds for person. For organizations, I was also thinking about something like an "institutional bibliography" where creators are persons affiliated with or payed by the organisation but the organisation itself wouldn't be listed as creator. Thus, an inverse property of creator or similar wouldn't fit.

Looking at Event. Are you looking for a property, similar to workPerformed, that would reference workPresented, or workProduced, or productProduced, or even thingProduced?

I was thinking about the papers of a conference that e.g. might be published on an OA repository and the slides that might be published on slideshare or similar with the conference organizers wishing to link the event to both.

Also wondering at your use of Action, to define the project. The OER Africa seems more Organization-like than Action-like to me.

You are right. It was submitted to us like this and we might adjust this before publication. (Just think about it as an organization and you have a good example for the organization use case where the org actually isn't creator of all resources.) It often is quite hard to type the different initiatives. For many things you don't know whether it is an organization, a project, a service, a community or many of these...

[RichardWallis]

OK so let's start with Person - new properties 'created' (range Thing?) & 'contributedTo' (range CreativeWork?, Event?, Action?, or just Thing?) would cover most of the use cases.

Those would also cover Organization, where the organization fulfills those specific roles too.

where creators are persons affiliated with or payed by the organisation but the organisation itself wouldn't be listed as creator

My initial thoughts on this are that if the Person is the creator and the person is a memberOf the Organization you have bases covered.

But then your "institutional bibliography" example made me think of a use of the new in bib.schema.org Collection with hasPart referencing the publication(s) and sourceOrganization referencing the organization/institution in question.

~Richard

[danbri]

It sounds more like foaf:publications than the inverse of author/creator/publisher, a pointer to a page that describes the publications.

[realworldobject]

Perhaps this?

schema:publications a rdf:Property; schema:domainIncludes schema:ProfilePage; schema:rangeIncludes schema:CollectionPage; .

a schema:ProfilePage; schema:about [ a schema:Person; schema:name “John Smith”; # etc. ]; schema:publications . All the publications could then be listed on the schema:CollectionPage, along with statements declaring the specific relationship between the person/organization and the CreativeWork(s) (schema:author, schema:illustrator, schema:publisher, etc.) Jeff From: Dan Brickley [mailto:notifications@github.com] Sent: Friday, August 14, 2015 2:01 PM To: schemaorg/schemaorg Subject: Re: [schemaorg] Add publications property (#736) It sounds more like foaf:publicationshttp://xmlns.com/foaf/spec/#term_publications than the inverse of author/creator/publisher, a pointer to a page that describes the publications. — Reply to this email directly or view it on GitHubhttps://github.com/schemaorg/schemaorg/issues/736#issuecomment-131195793.

[RichardWallis]

Not liking plurals I was thinking about a 'publication' property for Person/Organization with a range of CreativeWork. Unfortunately publication http://schema.org/publication is already used in a way that I don't think we could tweak to fit this requirement as well.

So what about:

schema:produced a rdf:Property; schema:domainIncludes schema:Person, scghema:Organization; schema:rangeIncludes schema:CreativeWork; .

That would enable you to relate to individual schema:CreativeWorks(s), or schema:Collection(s) or schema:CollectionPage(s)

~Richard

On Fri, Aug 14, 2015 at 7:10 PM, Jeffrey Young notifications@github.com wrote:

Perhaps this?

schema:publications a rdf:Property; schema:domainIncludes schema:ProfilePage; schema:rangeIncludes schema:CollectionPage; .

a schema:ProfilePage; schema:about [ a schema:Person; schema:name “John Smith”; # etc. ]; schema:publications . All the publications could then be listed on the schema:CollectionPage, along with statements declaring the specific relationship between the person/organization and the CreativeWork(s) (schema:author, schema:illustrator, schema:publisher, etc.) Jeff From: Dan Brickley [mailto:notifications@github.com] Sent: Friday, August 14, 2015 2:01 PM To: schemaorg/schemaorg Subject: Re: [schemaorg] Add publications property (#736) It sounds more like foaf:publications< http://xmlns.com/foaf/spec/#term_publications> than the inverse of author/creator/publisher, a pointer to a page that describes the publications. — Reply to this email directly or view it on GitHub< https://github.com/schemaorg/schemaorg/issues/736#issuecomment-131195793>. — Reply to this email directly or view it on GitHub https://github.com/schemaorg/schemaorg/issues/736#issuecomment-131197538 .

[ostephens]

Singluar possibilities

• publicationList
• listofPublications

[realworldobject]

Couldn’t the list of publications simply be treated as a schema:ProfilePage? The relationship between that that and the person/organization could then be expressed using schema:about in one direction and schema:url in the other. No new vocabulary would be needed.

Jeff

From: Owen Stephens [mailto:notifications@github.com] Sent: Friday, August 14, 2015 3:18 PM To: schemaorg/schemaorg Cc: Young,Jeff (OR) Subject: Re: [schemaorg] Add publications property (#736)

Singluar possibilities

• publicationList
• listofPublications

— Reply to this email directly or view it on GitHubhttps://github.com/schemaorg/schemaorg/issues/736#issuecomment-131213039.

[acka47]

I like @ostephens suggestion publicationList. @realworldobject's proposal wouldn't work for us. We already use schema:url for indicating a homepage and, thus, need a specific property.

[csarven]

I dislike the "list" approach because lists (ordered or not) are cumbersome to deal with when graph representations are serialized. A general term along the lines of foaf:made is a simpler way of handling this issue IMO.

Just to put this out there, another way of looking at this issue, although not simpler, is through qualified relations.

[mfenner]

What is the status of this? As this implemented somehow? My use case is similar to @acka47 I need need the inverse of author for CreativeWork, and I would like to see this as a new property instead of using @reverse. I have no strong preference for the name of the property, could be for example authored. I wouldn't use this property for the inverse of editor or contributor - these are less important use cases for me, so I might not need contributed.

[danbri]

Status is that our discussion above fizzled out. Maybe we can revisit and try grounding it in a specific markup example which we'll then improve to make a schema.org version?

[mfenner]

Using real-life data from DataCite:

{
  "@context": "http://schema.org",
  "@type": "Person",
  "@id": "http://orcid.org/0000-0003-0902-4386",
  "givenName": "Tom",
  "familyName": "Demeranville",
  "name": "Tom Demeranville",
  "authored": [
    {
      "@type": "ScholarlyArticle",
      "@id": "https://doi.org/10.6084/m9.figshare.4216323",
      "additionalType": "Paper",
      "name": "Project Identifiers",
      "description": "Presentation given at the PIDapalooza conference Reykjavik 9 November 2016.",
      "keywords": "80610 Information Systems Organisation",
      "dateCreated": "2016-11-08",
      "datePublished": "2016",
      "dateModified": "2016-11-16",
      "schemaVersion": "http://datacite.org/schema/kernel-3",
      "publisher": {
        "@type": "Organization",
        "name": "Figshare"
      },
      "provider": {
        "@type": "Organization",
        "name": "DataCite"
      }
    },
    {
      "@type": "ScholarlyArticle",
      "@id": "https://doi.org/10.5438/7885",
      "additionalType": "Report",
      "name": "Technical Considerations for an Organization Identifier Registry",
      "description": "Organizational identifiers are needed to help solve the affiliation use case in scholarlycommunication, i.e., which research outputs are produced by researchers affiliated to aparticular institution. Organizations need to be involved in changes to the organization identifierand associated metadata, including splitting or merging of organizations, and information aboutsub-organizations. Organizational identifiers must follow established best practices forpersistent identifiers, including the linking to other organization identifiers and other resources inthe metadata. This paper was prepared jointly by Crossref, DataCite, and ORCID andsummarizes technical use cases for an organizational identifier system, and our understandingof priorities based on community consultations carried out over the course of the past year.",
      "datePublished": "2016",
      "schemaVersion": "http://datacite.org/schema/kernel-4",
      "publisher": {
        "@type": "Organization",
        "name": "ORCID"
      },
      "provider": {
        "@type": "Organization",
        "name": "DataCite"
      }
    }
  ]
}

[TomDemeranville]

At ORCID our data is Person centric, so we would love to see some kind of attribution property from Person to CreativeWork. We're not overly concerned about the name but "created" or "contributedTo" makes the most sense to me as it's more general purpose than "authored". That said, I know Datacite have different meanings for contributor and creator, so would be happy with either.

Here's an example Person I mocked up a couple of days ago, as it would appear if I modelled it without this property:

       {"@context": "http://schema.org",
       "@type": "Person",
       "@id" : "https://orcid.org/1234",
        "email": "mailto:jane-doe@xyz.edu",
        "name": "Jane Doe",
        "givenName": "Jane",
        "familyName": "Doe",
        "alternateName" : "J Doe",
        "description" : "My bio would go here",
        "address":{

        },
       "@reverse": {
        "contributor": [
          {
            "@type": "CreativeWork",
            "@id" : "http://doi.org/10/1",
            "identifier" : {
                "@type": "PropertyValue",
              "propertyID": "PMCID",
              "value": "1234"
                },
            "name": "A journal article"
          },
          {
            "@type": "Dataset",
            "@id" : "http://doi.org/10/2",
            "name": "A dataset"
          }
        ],
        "funder":{ 
          "@type": "Organization",
          "@id" : "http://doi.org/10/3",
            "name": "My funder",
            "alternateName" : "the grant name",
            "identifier" : [{
              "@type": "PropertyValue",
              "propertyID": "Fundref",
              "value": "http://doi.org/10/3"
              },{
              "@type": "PropertyValue",
              "propertyID": "GrantNumber",
              "value": "abcd"
              }]
        }},
        "affiliation":{
            "@type": "Organization",
          "name": "My employer",
          "identifier" : {
                "@type": "PropertyValue",
              "propertyID": "RINGGOLD",
              "value": "1234"
                }
        },
        "alumniOf":{
          "@type": "Organization",
          "name": "My education provider",
          "identifier" : {
            "@type": "PropertyValue",
            "propertyID": "RINGGOLD",
            "value": "4321"
            }
        }
      }

As you can see, we have to reverse the relationships to CreativeWorks and Funders (which is a different discussion). One of the side effects of using @reverse is that it is easy to misinterpret. Things like the structured data testing tool see this metadata as representing two CreativeWorks and a funding organisation, rather than a person who's contributed to things and been paid to do it.

[mfenner]

DataCite (and Dublin Core) distinguish between author/creator and contributor, and schema.org does as well. I think the reverse properties could therefore be called authored and contributed respectively.

[acka47]

+1 for adding inverse properties. Instead of authored I think created is more important as it is the general property. contributed is also practical.

[TomDemeranville]

This is still an issue for us and holding up development.

At ORCID we have 4.6 million Person (researcher) records, managed by the researchers themselves. They're associated with 29 million CreativeWorks and over 4 million affiliations in our registry. We'd love to be able to expose this graph of scholarly communication metadata as schema.org.

Without this minor modification, the schema.org for an ORCID Person can easily be mis-interpreted as a collection of CreativeWorks with a single author each, or a collection of academic Funders each funding one Person. It's not ideal.

How can we move this issue forward?