[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ncISO UnidataDD2MI.xsl



we just switched toÂSaxon-HE-9.6.0-3.jar.

we tried changing version inÂUnidataDD2MI.xsl to 2.0, but it failed, so we changed to 1.0 and it seems ok.

On Thu, Apr 16, 2015 at 11:56 AM, Anna Milan - NOAA Federal <address@hidden> wrote:
Hi John,
Â
I'm testing thisÂUnidataDD2MI XSL with a couple different transform engines. Do you know which transform engine and version TDS is using?Â

Thanks,Â


Anna
*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*
Metadata Specialist

NOAA National Centers for Environmental Information
formerly NOAAâs National Geophysical Data Center

*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~*

On Wed, Apr 8, 2015 at 11:16 AM, John Caron <address@hidden> wrote:
Hi guys:

I changed the version to 1.0 and it seems to work ok. 2.0 failed. The file is in the TDS under WEB-INF/classes/resources/xsl/nciso/UnidataDD2MI.xsl .

I would like to know if you are using XSLT 2.0 features anywhere in ncISO?

John

On Tue, Apr 7, 2015 at 12:36 PM, Ted Habermann <address@hidden> wrote:
John,

I am forwarding this to Dave as I think he and Anna are shepherding this forward now...

Ted


On Apr 7, 2015, at 11:13 AM, John Caron <address@hidden> wrote:

Hi Ted:

We are seeing error messages from saxon parser on this file. Apparently because its labeled "version 1.1". Wikipedia says 1.1 was "abortive". Im wondering if we can change it to either 1.0 or 2.0?? Are you using 2.0 features ??



  • XSLT 2.0: after an abortive attempt to create a version 1.1 in 2001,[8]Âthe XSL working group joined forces with theÂXQueryÂworking group to createÂXPath 2.0,[9]Âwith a richer data model and type system based onÂXML Schema. The most recent version is XSLT 2.0,[10]Âdeveloped under the editorship ofÂMichael Kay. It reached recommendation status in January 2007.[11]ÂAs of 2010, however, XSLT 1.0[12]Âis still widely used, since 2.0 is not supported natively inÂweb browsersÂor for environments likeÂLAMP.

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:srv="http://www.isotc211.org/2005/srv" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:gsr="http://www.isotc211.org/2005/gsr" xmlns:gss="http://www.isotc211.org/2005/gss" xmlns:gts="http://www.isotc211.org/2005/gts" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:nc="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2" exclude-result-prefixes="nc">
<xd:doc xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl" scope="stylesheet">
<xd:desc>
Recent Modifications
<xd:p>2015-02-18. resolution value = missing when not available in NcML.</xd:p>
<xd:p>2015-01-16. fixed date error to prevent replacement of all spaces (' ') with a 'T' in the dates certain cases.</xd:p>
<xd:p>2014-11-25. fixed error that was outputting '::' at the end of a date.</xd:p>
<xd:p>2014-09-24. 1) Change all gmd:protocol entries of "http" to the valid entry of "WWW:LINK". There is no "http" valid in the list of gmd:protocol valids maintained at https://github.com/OSGeo/Cat-Interop/blob/master/LinkPropertyLookupTable2.csv. 2) gmd:protocol was missing from the NCDC climate and weather toolkit. I have added this entry with a value of "WWW:LINK".</xd:p>
<xd:p>2014-09-05. 1) Adds gmd:protocol elements to all service end points (srv:SV_ServiceIdentification) identifying them as either OPeNDAP:OPeNDAP, UNIDATA:NCSS, OGC:WMS, OGC:WCS, or OGC:SOS--the appropriate valids from this list: https://github.com/OSGeo/Cat-Interop/blob/master/LinkPropertyLookupTable2.csv. 2) Add GCMD Location Keywords from THREDDS catalog metadata: all "geospatialCoverage > name" entries. 3) Adds each "viewer" entry from the THREDDS catalog metadata as an additional gmd:distributorTransferOptions. John Maurer address@hidden</xd:p>
<xd:p>2014-07-24. test for null date and fixed another seconds since.... input. Translates UTC dates to ISO dateTime and 8601 basic dates to 8601 extended.</xd:p>
<xd:p>2014-07-17. updated dimensionResolution to handle many but not all ISO 8601 durations</xd:p>
<xd:p>2014-07-16. updated uom units for time to display only seconds or days when includes "days since..." or "seconds since..." text. </xd:p>
<xd:p> 2014-04-19. Changed order to look in CFMetadata group first in *unit variables. Added normalize-space dimensionResolution param to fix vertical units error. </xd:p>
<xd:p> 2012-05-11. 2.3 (slight revision): Changed the attribute name from coverage_type to coverage_content_type to be more correct and directly comparable to ISO....</xd:p>
<xd:p> May 10, 2012 version 2.3 authored by Ted Habermann</xd:p>
</xd:desc>
</xd:doc>


...






NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.