search

WGBH / PBCore2.0

Public Broadcasting Metadata Dictionary Project
http://www.pbcore.org
32 stars 9 forks source link

R11: Allow support for multiple expressions of time-based descriptive metadata within a single asset records. #13

Closed pdpinch closed 13 years ago

pdpinch commented 14 years ago

Segmentation is used for a variety of purposes. For example, when logging a file, a cataloguer may want to note than a celebrity was featured from minute 2 to minute 4. For rights management, it might be necessary to understand that a still photograph was featured, for which there are no rights to distribute online. From the perspective of navigation, organizations might need to insert chapter points into a video.

It is important to be able to describe segments of an asset and relate those to the whole, rather than have to create new PBCore records for each segment (and have flimsy relationships between segments and assets).

pdpinch commented 14 years ago

Peter and Dave M are debating whether to add a startTime and endTime attribute to certain elements, or just recommending PBCore authors create multiple records with relationships.

At the moment, Dave M is leaning towards using attributes.

pdpinch commented 13 years ago

in 3fcbe9d4de685c36301d3e1ab86c99b12ae06773, description has a type of descriptionStringType, which has startTime and endTime attributes. This allows descriptions to be segmented.

However, this does not address segmentation of rights, which may be out of scope.

kvanmalssen commented 13 years ago

I like the solution of using descriptionStringType with startTime and endTime attributes. Just not sure what segmentType means here. I know this is a documentation issue, just wanted to make a note of it.

jackbrighton commented 13 years ago

I love the suggestion to allow (optional) startTime and endTime attributes to multiple elements. Seems like this could work for rightsSummary too without mucking up the works. It would work for subjects, contributors, and even coverage.

MarcosSueiro commented 13 years ago

I would again suggest ISO 8601 for this. It allows for start/end, start/duration and other formats; is machine readable; and it fits in just one field. http://www.iso.org/iso/date_and_time_format

jackbrighton commented 13 years ago

Agreed!

pdpinch commented 13 years ago

We have written How To to go with the schema change.