[utypes] (no subject)

[Omar Laurino]

Hi Mireille,

I see your point about versioning. I guess we can drop the versioning of
the single entity and use it for the entire namespace. At that point,
though, we have two options: either we keep the namespace label (e.g. char)
fixed and we add the versioning string to it (char-1.1) or we include a
dynamic mechanism for namespace declaration, a la XML.

However, in your response I don't understand this:


> We dicussed how a customised new entity could be derived from an existing
> one in order to extend data models for some specific configurations. This
> means this extra entities are specified outside any data model , but
> documented in the service , application that is using it.
> I think this can be hooked as a derived class of entity in a specific
> CustomisedEntity
>
>
This is in my example, that's why I am not sure I understand. One of the
main points of the suggestion is that you can create a custom entity in a
standard way, instead of being forced to use standard entities (which you
would still have). A VO-enabled application will know about the standard
way and will make sense of the file even though the entity itself is not
standard (it will make even more sense if the entity *is* standard). I
don't get where the CustomizedEntity class comes into the picture. Could
you please elaborate?

Thanks,

Omar.

-- 
Omar Laurino
Smithsonian Astrophysical Observatory
Harvard-Smithsonian Center for Astrophysics
100 Acorn Park Dr. R-376 MS-81
02140 Cambridge, MA
(617) 495-7227
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/utypes/attachments/20120207/f2eed114/attachment.html>