Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
> Discuss putting wildcards in NcML URI that are passed to IOSPs (for
> Are these the advantages: for REST calls, the URI is shown in the
> NcML instead of being hidden in source code and if URI changes,
> recompile is not necessary, only change to NcML?
The general answer is that you can put about anything in the NcML that
your IOSP wants. NcML specifies a few XML attributes that it will look
for within a "netcdf" element
The ones that affect us are "location" which must point to something
that it can open as a RandomAccessFile and "iosp" which identifies the
class to use as the implementation of the IOSP interface. You can add
about anything else that your ISOP might want. You can even set location
to "/dev/null" and manage your own data access. The question then
becomes, can we use some convention more broadly.
I don't quite understand the use case. I assume we are talking about:
1) an IOSP that delegates to a service to access data,
2) whose parameters names could change (e.g. "start" to "begin"), or
3) whose time format could change
Is that the idea?