New pbcoreRightsType and pbcoreRightsNote elements

[AllisonAnn]

New pbcoreRightsType and pbcoreRightsNote elements

I think it would make the pbcoreRightsSummary element more useful, if it had rightsType and rightsNote sibling elements available for additional definition and context. Each element would have the @source, @ref, @version, @annotation attributes associated with it.

The rightsType element would also need a controlled vocabulary developed for it. We might start with the following types:

Broadcast | Clearance [Music | Performance | Publication | Visual Art] | Copyright | Distribution [3rd Party | Digital Media | Download | Streaming] | Reproduction | Restrictions | Terms of Use

<pbcoreRights>
    <pbcoreRightsSummary source="" ref="" version="" annotation="">©2014 National Center for Audio Experimentation</pbcoreRightsSummary>
    <pbcoreRightsType source="" ref="" version="" annotation="">Copyright</pbcoreRightsType>
    <pbcoreRightsNote source="" ref="" version="" annotation="">In perpetuity…blah blah blah</pbcoreRigthsNote>
</pbcoreRights>
```xml

I'm not sure how this would work with the current rightsLink and rightsEmbedded fields…but we could probably work it out.

[awead]

You'll find you'll have difficulties if you have multiple rights statements and you need to sort out which notes are part of which. For example, if you have one type that's a copyright and one that's an embargo, for example, how do you know which note is for that embargo and which is for the copyright?

If you assign attributes to the pcboreRights node itself, it's much clearer to query:

<pbcoreRights source="some authority" ref="http://example.com/copyright" annotation="copyright">
  <pbcoreRightsSummary>Copyright, etc.</pbcoreRightsSummary>
  <pbcoreRightsNote>In perpetuity, etc.</pbcoreRightsNote>
</pbcoreRights>
<pbcoreRights source="some authority" ref="http://example.com/embargo" annotation="embargo">
  <pbcoreRightsSummary>Under embargo until 12/31/2015</pbcoreRightsSummary>
  <pbcoreRightsNote>More explanation here...</pbcoreRightsNote>
</pbcoreRights>

You can also use attributes to the summary and note nodes if you need to define authorities to those specific statements.

[AllisonAnn]

That looks like a good solution. I wonder if adding an @term="copyright" attribute would be useful for term controlled fields? The way you've coded it - while the term does work in the @annotation field, I wonder if anyone would want to use @annotation for an element description or use type note....and in that case, an @term attribute would be better?

The only reason I suggest this is more recently, I've begun to think of the @annotation attribute as similar the @title html attribute, that can be used as pop up help, or, to help explain the element for visually impaired people. Not that the term "copyright" wouldn't suffice...I just wonder if we need both @term and @annotation for added flexibility?

[awead]

@AllisonAnn that's a good point... for all I know, I may not be using @ref correctly either, since I think it's supposed to point to the authority organization and not the specific term. Are there any exemplars we can look to here? I don't know of any authority services for rights.

[AllisonAnn]

It's unclear if @ref should point to an authority, or, to a specific term. I would think it should link to the specific term, though.

Also, maybe the attribute should be called @type instead of @term, so that it is more descriptive of its relationship/role to the element?

[AllisonAnn]

Actually - @rightsType as the attribute name would follow how other [element]Type attributes have already been structured.

<pbcoreRights rightsType="copyright" source="some authority" ref="http://example.com/copyright" annotation="blah blah blah">
  <pbcoreRightsSummary>(c)2014 blah blah</pbcoreRightsSummary>
  <pbcoreRightsNote>In perpetuity, etc.</pbcoreRightsNote>
</pbcoreRights>
<pbcoreRights rightsType="embargo" source="some authority" ref="http://example.com/embargo" annotation="blah blah blah">
  <pbcoreRightsSummary>Under embargo until 12/31/2015</pbcoreRightsSummary>
  <pbcoreRightsNote>More explanation here...</pbcoreRightsNote>
</pbcoreRights>

This example could work very well too, as an illustration for how other elements needing a nested note element for context, could be structured.

[awead]

Looks great! BTW, I took the small liberty of editing your comment. The "xml" at the end of the three backticks is only required at the beginning of the block, but is closed with just the three backticks again and no "xml" at the end.

[AllisonAnn]

Thanks! hahaha

On Tue, Aug 5, 2014 at 7:54 PM, Adam Wead notifications@github.com wrote:

Looks great! BTW, I took the small liberty of editing your comment. The "xml" at the end of the three backticks is only required at the beginning of the block, but is closed with just the three backticks again and no "xml" at the end.

— Reply to this email directly or view it on GitHub https://github.com/WGBH/PBCore2.0/issues/62#issuecomment-51281580.