NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Ethan Davis wrote:
Hi Benno,I will go through our catalogs and add the xlink:type attribute. I'll also add it to our catalog generation tools.
That would be great.
my reading of xlink is that xlink:type is required, and the way we are using xlink its value is "simple".In the InvCatalog 0.6 spec xlink:type had a default value of "simple". Looks like that got dropped in 1.0. Does adding this as a default seem like a good idea? Or would requiring it but no default value be preferable?
There is no provision for a default value.The reason for doing this is so that we can build on top of software that already understands xlink, which, if we have not written it, is expecting xlink:type="simple" before processing it.
Benno -- Dr. M. Benno Blumenthal benno@xxxxxxxxxxxxxxxx International Research Institute for climate prediction The Earth Institute at Columbia University Lamont Campus, Palisades NY 10964-8000 (845) 680-4450
thredds archives: