> Could we think about something like spectrum.load.table, spectrum.load.file
> and spectrum.load.url? Or something like this, these are the first names I
> could think of, but my idea is to differentiate the sources (files and
> URLs).
The MType vocabulary is far from complete at this stage, and
adding something
like spectrum.load.url (and spectrum.load.text) is easy to do at this point.
Where I think we still need some discussion is in how we define 'table' or 'image'. For example, does a spectrum in a table mean a VOTable or a FITS table or an ASCII table? Do we want to define this exactly or do we need additional types such as spectrum.load.votable, spectrum.load.fitstable, etc? Or, do we leave it as just 'table' and let the apps decide whether they can read the format and ignore it if they can't?
Cheers,
-Mike
Received on 2008-05-08Z19:46:38