> now I just got back to the CMDI profiles once again, trying to
> incorporate some of the components or DCs the BAS and/or Tübingen
> profiles use to assure we at least have something in common although
> nobody knows how that part works yet:) Anyway, again I stumbled upon
> something: The component cmdi-access used in cmdi-COLLECTION is - I
> guess - one of those old "hand-made" components (in fact there are a
> lot of those old cmdi-something components) and for the element
> Availability, the cardinality is 1-1 in the component registry as View
> or XML, but 1-unbounded if I download the XSD for e.g. the
> SpeechCorpusProfile or the media-corpus-profile using this component.
Hi Hana,

Good observation. In this case it is because the multilinguality flag of
Availability is true. This always makes an element repeatable, even if
MaxOccurrences is set to a fixed value (like 1). I added a note about
this to the relevant FAQ:

> The same thing applies for the cmdi-totalsize component's Element
> SizeUnit. In this case however the cardinality 1-1 seems to be more
> adequate, i.e. the one displayed in the component registry, not the
> one in the schema.
This is the same case.

> For all but the Validation element in
> cmdi-validation, the component registry says 0-1 and the schema says
> 0-unbounded. I suppose in the end the schema counts, but I was just
> wondering if someone has checked all these cmdi-something components
> for these old cardinality errors (if that's even the problem here, I
> can't really remember if this is the same behaviour). I haven't, and
> these might be extremely rare cases or not, I don't know. If these old
> components still need some correcting maybe someone should have a look
> at it before we start creating CMDI instances and/or CMDI generating
> stylesheets at the centres?
The most serious result of enabling the multilinguality option is indeed
that a field might be repeated, even if the profile creator fixed it to
a max nr.

@Twan: maybe we can grey out the MaxCardinality in the component editor
when someone selects multilingual? That would alert the modeller
immediately about the effects.

related question, same source:

> another thing I was wondering about is the fact that some components
> (OriginLocation in the cmdi-COLLECTION component, the TimeCoverage
> component in the cmdi-generalinfo and the BirthCountry component of
> cmdi-actor) don't seem to have component ids, and can't be found when
> searching the registry. Are they somehow "private" components that
> shouldn't be reused on their own or has the component id simply been
> lost somewhere along the way? I wanted to reuse the BirthCountry
> component, but *not* the entire "parent" Actor component, but I don't
> know if this should be possible (I suppose I could save the cmdi-actor
> as our new component and the adapt this one, but this includes a bit
> more work than I wanted, since I already have a component...). And the
> lack of component ids might be problematic for future
> harvesting/searching?
Hi Hana,

these are embedded components; it is indeed possible to include a
component that does not exists as a separate entity in another
component. If you want to use such a component nevertheless, you will
need to make a copy of the containing component, remove the useless
elements/components and store it as a new component.

Last modified 12 years ago Last modified on 06/06/12 14:01:28