concept representation/displaying language?

[Carlos Rodrigo Blanco]

Unless you use a UCD that only can be understood as "look into this url to 
get the meaning of this param"; and there you get the "displaying of 
the thing", even an image, and you could also get the physically 
meaningfull UCD (for instance, phys.temperature), etc.

It's another creative trick. I see that, at least, I' not the only one 
interested in this. It would be nice if we could have a "common trick" 
(that is, something like an specification) so that each one could 
understand each other's tricks :-)

Carlos

On Fri, 5 Jun 2009, Matthew Graham wrote:

> Hi,
>
> But "meta.id" would be just as valid a UCD as "meta.ref.ivorn" for IVORN. 
> Using a semantic descriptor to determine presentation issues is a dangerous 
> practice.
>
> 	Cheers,
>
> 	Matthew
>
>
> On Jun 5, 2009, at 8:04 AM, Roy Williams wrote:
>
>> On Wed, 3 Jun 2009, Carlos Rodrigo Blanco wrote:
>> 
>>>>> In some cases, we have to include in VOTables quantities (params, 
>>>>> fields...)
>>>>> that are not predefined in a protocol or data model or whatever (the 
>>>>> point is:
>>>>> no application will have a precoded way to handle it) I would like to be 
>>>>> able to tell the client (application) how that quantity should be 
>>>>> displayed (formated).
>> 
>> Francois, Mark,
>> 
>> A very simple trick I have been doing in my applications is to use the UCD 
>> to determine presentation: if the ucd is "meta.ref.url", then the value is 
>> known to be a URL link, and treated accordingly. Similarly with 
>> meta.ref.ivorn.
>> 
>> Roy
>> 
>> -- 
>> 
>> California Institute of Technology
>> 626 395 3670
>