Example API 2.0 files

[acka47]

To give @dr0i some more guidance for working on API 2.0 issues it would be nice for him to have some examples of how the desired structure should look like.

[acka47]

I managed to create three example files. They probably won't work as test files as I have probably made minor mistakes or might have forgot some changes but in general they should provide good guidance:

• CT003012479.json
• HT013304490.json
• TT002234459.json

Note that this also is not the final state we should have in API 2.0. One problem with TT002234459.json I described in #8 (comment).

[acka47]

Where needed, I adjusted the examples according to #38 (comment), see these revisions of the files:

• CT003012479.json
• TT002234459.json

[dr0i]

In the mentioned CT003012479 there is a dateOf property as part of a person entity. At the moment we use these life dates only for subjects (field 9[01234][27]-[-12].d). Should we want to take life dates for person entities which are no subjects also into account we should make a new issue.

[acka47]

I removed the dates from the example.

[dr0i]

Compared your files with the staging index. Difference:
In CT003012479 you listed 14216075X two times (quote right, as in the source http://lobid.org/hbz01/CT003012479 this person is also mentioned in field 800 as "Sprecher") whereas in http://test.lobid.org/resources/CT003012479#! there is only one mentioning of her. The two appearances of the person seems a bit superflous to me, though, because she is first roled as an actress and then as a contributor whereas , I think, every agent in the contribution-list is implicitly a contributor.

At the moment the 8xx-fields are not analyzed thus the role ("Sprecher") is ignored. I assume that that leads to the merged one mentioning of the person.
What shall we do? Take roles of 8xx-fields also into account? The person would then appear one time with two roles: actress and speaker.

[acka47]

Generally, I think it is ok to only list a person once when it is mentioned twice in the source but one role is just Contributor. I also agree that we shouldn't take into account 8xx fields.

But I don't think it is ok to list two roles in one contribution object. If a person has two roles in a work (e.g. "Sprecher" and "Darsteller") these are actually two contributions with different roles but not one contribution covering two roles.

[dr0i]

These example files are a bit out of date, but as @acka47 just said we won't update these examples. I compared them with the staging data and find them fitting.
So +1 for me for closing, assigning @acka47 .

[acka47]

But I don't think it is ok to list two roles in one contribution object. If a person has two roles in a work (e.g. "Sprecher" and "Darsteller") these are actually two contributions with different roles but not one contribution covering two roles.

I posted this question to the Bibframe list and Ray Denenberg just confirmed what I said. Quoting Ray:

If you want to list two roles, e.g. “illustrator” and “author” for the
same person, the rule is, declare two separate Contribution resources.
Two or more role statements within the same Contribution resource should
occur only because you want to provide two different representations
(e.g. two different URIs) for the same role.

[acka47]

Closing.