Comments on: instantiationLanguage http://www.pbcore.org Public Broadcasting Metadata Dictionary Project Sat, 19 Nov 2011 15:23:52 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Jack Brighton http://www.pbcore.org/v2/elements/pbcoredescriptiondocument/pbcoreinstantiation/instantiationlanguage/comment-page-1/#comment-413 Jack Brighton Fri, 14 Oct 2011 16:33:59 +0000 http://pbcore.org/#comment-413 I second Dave's motion. Martina McGinn added this on the PBCore Talk listserv: "I agree and suggest that instantiationAlternativeModes could also warrant multiple occurrences (e.g. a film dubbed in English and sub- titled in Spanish). And it seems logical that if instantiationLanguage allows multiple occurrences then so should essenceTrackLanguage." Seems like a minor schema tweak would iron out these rough spots. But of course there are others, and we need to follow through on identifying them, like this one. Jack I second Dave’s motion.

Martina McGinn added this on the PBCore Talk listserv:
“I agree and suggest that instantiationAlternativeModes could also
warrant multiple occurrences (e.g. a film dubbed in English and sub-
titled in Spanish). And it seems logical that if instantiationLanguage
allows multiple occurrences then so should essenceTrackLanguage.”

Seems like a minor schema tweak would iron out these rough spots. But of course there are others, and we need to follow through on identifying them, like this one.

Jack

]]> By: Dave Rice http://www.pbcore.org/v2/elements/pbcoredescriptiondocument/pbcoreinstantiation/instantiationlanguage/comment-page-1/#comment-330 Dave Rice Mon, 08 Aug 2011 20:20:46 +0000 http://pbcore.org/#comment-330 The strange formatting of this field makes handling these values really challenging. Since PBCore is expressed in XML, I recommend that instantiationLanguage simply be maxOccurs = unbounded. The odd manner of handling language expressions as semicolon-delimited strings is inconsistent with the rest of the standard and a hassle to manage when building or parsing a PBCore document. For example, having: <instantiationLanguage>eng</instantiationLanguage> <instantiationLanguage>spa</instantiationLanguage> would be a lot more convenient, then having to deal with the string parsing inside: <instantiationLanguage>eng;spa</instantiationLanguage> Dave The strange formatting of this field makes handling these values really challenging. Since PBCore is expressed in XML, I recommend that instantiationLanguage simply be maxOccurs = unbounded. The odd manner of handling language expressions as semicolon-delimited strings is inconsistent with the rest of the standard and a hassle to manage when building or parsing a PBCore document.

For example, having:

<instantiationLanguage>eng</instantiationLanguage>
<instantiationLanguage>spa</instantiationLanguage>

would be a lot more convenient, then having to deal with the string parsing inside:

<instantiationLanguage>eng;spa</instantiationLanguage>

Dave

]]>