issues
search
WGBH
/
PBCore2.0
Public Broadcasting Metadata Dictionary Project
http://www.pbcore.org
32
stars
9
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Metadata Registry lists wrong URI for vocabs
#50
caseyedavis12
opened
10 years ago
0
Allow for @source attributions for both pbcoreDescription and descriptionType
#49
kvanmalssen
opened
10 years ago
8
Allow for @source declarations for both title and titleType
#48
kvanmalssen
opened
10 years ago
12
broken link InstantiationRelationType
#47
laurensorensen
opened
10 years ago
0
Create new technicalStringType element InstantiationDimensions with maxOccur=unbounded
#46
MarcosSueiro
closed
10 years ago
0
Create new essenceTrackPlaybackSpeed element of technicalStringType
#45
MarcosSueiro
closed
10 years ago
0
Change formatFileSize to a repeatable formatSize with unitType (and possibly annotation)
#44
MarcosSueiro
opened
13 years ago
0
make essenceTrackIdentifier unbounded
#43
MarcosSueiro
closed
10 years ago
4
Creator, Contributor, Publisher
#42
MarcosSueiro
opened
13 years ago
1
Do we still need subjectAuthorityUsed?
#41
dmaccarn
closed
10 years ago
4
essenceTrackIdentifierSource should be of type sourceVersionStringType instead of xsd:string
#40
pdpinch
closed
10 years ago
4
use of sourceVersionGroup at instantiationIdentifierSource and genreAuthorityUsed?
#39
WeAreAVP
closed
10 years ago
6
allow instantiation at the top level
#38
WeAreAVP
closed
13 years ago
16
Few minor semantics issues in use of minOccurs.
#37
WeAreAVP
closed
13 years ago
5
pbcoreAssetType
#36
WeAreAVP
closed
10 years ago
3
openness of schemaVersion
#35
WeAreAVP
closed
10 years ago
8
Remove genreAuthorityUsed in favor of genre @source attribute ?
#34
pdpinch
closed
10 years ago
7
R28b: Resolve overlap between source attribute and subjectAuthorityUsed/genreAuthorityUsed
#33
pdpinch
closed
13 years ago
1
R28a: Provide guidance and clarification on use of source and version attributes.
#32
pdpinch
closed
13 years ago
2
R27: API documentation
#31
pdpinch
opened
14 years ago
0
R26b: need to express instantiation-specific rights statements
#30
pdpinch
closed
14 years ago
2
R26a: Provide guidance on how to or provide specific means to document information of the relationship being instantiations of an asset.
#29
pdpinch
closed
13 years ago
6
R25: Allow classification of rightsSummary statements
#28
pdpinch
closed
13 years ago
4
R24: Relation Element
#27
pdpinch
closed
14 years ago
1
R23: Allow complex coverage statements (as in PBCore 1.0)
#26
pdpinch
closed
13 years ago
3
R22: Allow or provide guidance on validatable expression of multiple PBCore assets within a single XML document/feed.
#25
pdpinch
closed
13 years ago
6
R21: Support subjectTypes (similar to MODS, MARC, and others)
#24
pdpinch
closed
13 years ago
3
R20: Recommend ISO 639-3
#23
pdpinch
closed
13 years ago
3
R19: Allow support for Linked Data
#22
pdpinch
closed
10 years ago
9
R18: Guide support for non-unique identifiers such as episode numbers, chapter numbers, series numbers, series identifiers, and other identifiers.
#21
pdpinch
closed
13 years ago
2
R17b: Additional adjust minOccurs to prevent semantically unclear expressions.
#20
pdpinch
closed
13 years ago
3
R17a: Remove semantically-meaningless ordering requirements for PBCore elements
#19
pdpinch
closed
10 years ago
3
R16: Updates to extension and annotation (and essenceTrack annotation) structure.
#18
pdpinch
closed
14 years ago
2
R15: Technical Vocabulary Review and Additions, Make the namespace, title, and version of recommended vocabularies more clear (to facilitate better integration in source and version attributes)
#17
pdpinch
opened
14 years ago
0
R14: Descriptive Vocabulary Review and Additions, Make the namespace, title, and version of recommended vocabularies more clear (to facilitate better integration in source and version attributes)
#16
pdpinch
opened
14 years ago
1
R13: Allow support for inline XML (xsd:any) within extension, rights, and (maybe) description.
#15
pdpinch
closed
14 years ago
2
R12: Add a 'unit_of_measurement' attribute on appropriate technical metadata fields.
#14
pdpinch
closed
10 years ago
5
R11: Allow support for multiple expressions of time-based descriptive metadata within a single asset records.
#13
pdpinch
closed
13 years ago
7
R10: Clarification of formatStandard and formatEncoding
#12
pdpinch
closed
13 years ago
9
R8: Provide guidance on fulfillment of PBCore's technical metadata.
#11
pdpinch
opened
14 years ago
1
R7: For technical fields (such as frameSize, bitDepth, frameRate), position the controlled vocabularies as recommendations of expression and not the definitive list.
#10
pdpinch
closed
13 years ago
6
R6: Allow for multiple expressions of formatGenerations inside an instantiation.
#9
pdpinch
closed
13 years ago
3
R5: Adjust language regex to allow for empty <language> elements.
#8
pdpinch
closed
14 years ago
3
R4: Provide recommendations to identify/describe asset types that do not conform to the typical TV-Guide-style genre lists (such as pre-production classifications of content such as interview, broll, stock footage, sot, outtakes, etc)
#7
pdpinch
closed
13 years ago
12
R3: Allow management of dates and types of dates that pertain to the intellectual content of the asset (beyond coverage_spatial).
#6
pdpinch
closed
10 years ago
21
R2: Guidance on PBCore Profile Development
#5
pdpinch
opened
14 years ago
4
R1c: For creator, contributor, and publisher provide support for management of (c) additional roles.
#4
pdpinch
closed
13 years ago
3
R1b: For creator, contributor, and publisher provide support for management of (b) character portrayal (contributor only?),
#3
pdpinch
closed
13 years ago
11
R1a: For creator, contributor, and publisher provide support for management of (a) affiliation,
#2
pdpinch
closed
13 years ago
3
R1: For creator, contributor, and publisher provide support for management of (a) affiliation, (b) character portrayal (contributor only?), and (c) additional roles.
#1
pdpinch
closed
14 years ago
1
Previous
Next