Search results

web. Both the produced XSLT XML file and the REST service will be provided to the Federation for use by the members, with the XSLT being licensed under an

record was imported. Option 1-- add capability to pass response xml through xslt in output pipe line. Alternatively extend the machinery that does the ATOM

XSL: http://capita.wustl.edu/xslt/XSL_WCS_GETCAP_TO_ISO.xsl WMS GetCapabilities to ISO 19115 XSL: http://capita.wustl.edu/xslt/XSL_WMS_GETCAP_TO_ISO.xsl GEOSS

"low-hanging fruit" ways of accessing services Shell script w/ wget/curl XSLT Idea is to show people how easy it is to access discovery services Ruth:

assumption is entirely wrong. Here is a fragment of an ERD generated from the DIF XSLT. To complete the ERD another 15+ tables would need to be added to account

specific format for the response Unless the response is renderable (i.e., with XSLT) None, Chris has been looking into the format for these specs Brainstorming

transforms will expose additional information to the user interface. The XSLT processors we'll try out are your modern browser Saxon-HE 9.4 (open source

statewide DOQQ data acquisition) Z39.50 Web-accessible directory Customized XSLT/SOAP metadata rendering service FGDC Clearinghouse Node (Z39.50) Geospatial

Same as procedure in step one, using "--outputFormat rdf/xml" Option 2: Use XSLT to make custom transformations of our XML output into RDF Our XML Schema

schema-aware editing, validation using schema or schematron, transformations using XSLT, remote access to files and transforms, tagless editing, and batch processing

translate these dates into the more structured formats required by ISO. If using XSLT's to translate FGDC date content to ISO (such as the NOAA transforms), logic