differences in ISO xml when generated with ncISO and Thredds

[zdefne-usgs]

Based on the comparison with the xml generated with ufncISO:
java -Xms1024m -Xmx1024m -jar ncISO-2.3.5.jar -ts http://geoport-dev.whoi.edu/thredds/sand/usgs/Projects/BBLEH/run071tRX/catalog.xml -num 1 -depth 20 -iso true

1
There are a couple of major differences between the ISO metadata generated with the Thredds ISO service and the ISO metadata generated with the ncISO, such as the fileIdentifier and the dimensions.

As reading the recommendations looks like one should combine the naming authority and the id to put back into the id field. The combination of the "naming authority" and the "id" should be a globally unique identifier for the dataset. It is recommended that the combination should be unique, but they are separate fields. ncISO does not do it either (or is it because Thredds server already automatically combine the two to get the unique identifier?).

2
Treatment of dimensions has changed in ncISO. See Dimension_Information. In addition to the temporal, vertical and topoloigcal dimensions there are now dimensions for column, row, tracers, boundary, xi-, eta- (rho, psi) and s-(w, rho).

3
Thredds netcdf http service is missing in ncISO and the netcdf subset service definition is simplified (has less fields). The solution may be using ncISO, but need find out why http service is not described.

4
However, in neither of them MD_Georeferenceable spatial representation is not automatically generated.