ImageDM: what does extension mean?

[CresitelloDittmar, Mark]

Francois/Mireille,

I seem to have caused some confusion on this point...

Ray> Should a client that is only ObsCore-aware be able to interpret the
ObsCore portion of an ImageDM serialization?
Mark>

Optimally, an ObsCore aware application should be able to ignore the
prefix and recognize the content.  This would probably work, but only
because
 it is a TOP level model.

This is similar to discussions which went on for lower level objects, where
the
 practice of combining utype strings make it impossible for a generic
utility
to identify the axes (for example) within a model an plot them.

 Francois> Mark, are you addressing the problem of combining char2 and stc
utypes strings for example ?
Mireille>  More precisely , are you addressing here the problem of
ObservableAxis vs FluxAxis?

I think Francois is closer.  I was trying to say that our current practice
of generating Utypes as a concatenation
of the path to the incorporated element tree with path of the element,
makes it impossible (in general) for a
generic application to recognize the piece it knows once it is embedded
into a new model.
Well, I guess it could, if it weren't also mandated that a Utype is not to
be treated as a path, but just as
a text string.

For Observation elements, this is less true, since it sits at the top level
of these models, the utypes
for those elements won't change much, if at all.. other than the prefix.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/dm/attachments/20131031/985e8257/attachment.html>