The following is an IM session I had today with Sylvia. The conclusion of which is that the long name, short name, and description of every component in a model component tree needs to have the long name, short name, and description respectively of a corresponding simulation concatenated to it.

the xml has a shortname, longname, and description for both the components and the simulations
julien took the longname and displayed it as the rdfs:name for the instance
I believe we want the short name there
the longname should become the fullname
we basically want both displayed
this is what it will end up as:
component shortname + simulation shortname = rdfs comment
component longname + simulation longname = fullname
oops
that should be rdfs: label
component description + simulation description = rdfs: comment

So, a question about what is visible on the curator site at the moment.
In the component tree on the left, the long name is listed if available, otherwise the short name is listed.  Is that still what needs to happen?
Sylvia Murphy
what we were told, was that the metafor folks were going to prefill in the short names for everyones component tree
there are something like 22 modeling centers participating.
so, I believe that short name will always be there b/c of that
10:31 AM
it is up to the user though to put in a long name
to distiguishe empty info, we prepended the default with a SN
for short name
that lets us know that that component was not actually filled in
whether we want to do that in the final, if we actually get empty stuff I don't know.
at one point i requested that if a component is empty they not export it.
10:33 AM
not sure what happened with that request...

in a CIM document, there will only be a model component tree and simulation for one model/simulation, correct?
Sylvia Murphy
yes
that is what I have been told
wilcox.hannah@ymail.com
of course.  so unless you've been lied to, I won't have to worry about matching a simulation to a model within a document?
Sylvia Murphy
correct
even if god forbid there is more than one simulation in a CIM record set, you would just loop over them and concatinate the names to create 2 separate CIM trees.
I don't see that know, knock on wood.
10:37 AM
though...