fiafcore:Codec #135
Replies: 3 comments
|
Wondering if keeping a controlled list would have the problem of being outdated very quickly. I see two ways:
|
|
Using values rather than entities would make life easier in the short term ("strings not things!"), but I would be concerned that this would allow a plurality of terms for what is ultimately the same thing. As an example, listed synonyms for wd:Q212633: MPEG-4 Part 10, Advanced Video Coding, MPEG-4 Advanced Video Coding, ISO/IEC MPEG-4 AVC, MPEG-4 Part 10, MPEG-4 AVC, H.264/MPEG-4 Part 10, H.264/AVC, H.264, h264, H264, H.26L, AVC, H.264/ISO/IEC 14496-10—MPEG-4 Part 10 Advanced Video Coding, H.264/MPEG-4 AVC... Also noting that presumably tools like MediaInfo already have a standardized vocabulary in place? My current thinking is whether we should park these granular digital properties for the time being, and look instead to federate ontologies with the OWL version of PREMIS, which already includes some fairly mature structures for streams/containers, PRONOM, etc. Keen for other opinions on this, as I also do absolutely see the value in supporting queries for, eg, "how much of the community is using FFv1", "is my digitised copy of a film using a lossless/lossy codec as opposed to yours", but I think for now I would label as |
|
I agree: using an existing list would be useful. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Definition
From the Moving Image Cataloguing Manual pg. 75:
From the Moving Image Cataloguing Manual pg. 75:
D.7.10 Item Codec type contains a vocabulary for this concept, with the following terms:
Vocabularies
BFI
[Item] xpath .//code_typeBundesarchiv
[Item] xpath .//ba:Exemplar/ba:CodecBild[Item] xpath .//ba:Exemplar/ba:CodecTonRecommendation
Do not include vocabulary for the next iteration.
All reactions