<Quote>
I'm also not sure if this name changes over time or if it is fixed once
defined. Maybe somebody with more CCTS experience can clarify that.
</Quote>
Since the Dictionary Entry Name is comprised of the individual ISO/IEC
11179 data element terms (Object Class, Property Term, Representation
Term, plus Qualifiers), it should not be static. Users may certainly
have a need to change the name of (for example) an Object Class, which
should propagate to the Dictionary Entry Name.
Joe
Diego Ballvé wrote:
>
> > >- DictionaryEntryName is composed of parts. Shall the parts
> > >be stored in the ExtrinsicObject, they probably will not be
> > >interanionalized. Not sure if they would need to anyway,
> > >but modellers here defined them in Finnish, not English.
> > >
> > I did not realize that at first.
> >
> > If we need to keep the components of DisctionaryEntryName
> > distinct then
> > we should not map it to Name but to a Slot where each
> > component can be a
> > value. The name could show the concatenation of the values
> > for convenience.
>
> Actually I haven't kept them in my model that is in use.
> Just the concatenated name. I'm also not sure if this name
> changes over time or if it is fixed once defined. Maybe
> somebody with more CCTS experience can clarify that.
>
> Gotta leave now. Farrukh, I'll answer the rest tommorrow.
>
> Diego
