GeoWeb Page

GeoWeb 2008

These are third party software and data sets.
Not owned by GeoWeb.

Any papers or workshops presented at GeoWeb conferences are owned by GeoWeb, available for purchase separately (from GeoWeb) or by paid attendance at the conference.
There is no free download available of these items.

What's on this page?
* Open Source Programs (from 3rd parties)
* data sets, such as XML, KML, SVG, which are not being sold but have IP rights associated
* comments, some technical descriptions, and orientation information

There are no management overviews on this page, you have to have a certain minimum background in computing technology to make use of the content of this page, called 'the entry level'. There are myriad courses in many places that explain how to use these open source programs. It is up to you to understand or figure out any 'value' of the content of the things on this page.

The page will be updated with requisite technology knowledge level / 'background' for productive use of the concepts / data sets provided here. You will gain insight into the material by looking at other pages on this website. The website is about ontologies, robotics and other such things, only this page is constrained to geospatial stuff.

press the button

Notepad++

Protege/Owl, register to download Protege itself (free). Get the FULL version it has 15 plugins of interest.

Pellet, it is a reasoning program. If you get FULL Protege first you do not need this download.

Jena, it is a reasoning program. If you get FULL Protege first you do not need this download.

SWRL, Semantic Web Rule Language. If you get FULL Protege first you do not need this download.

SAXON B 9 XSLT , by Michael Kay, has XSLT extensions, works w/ Java, & your own eventhandlers *

Firefox 3, built-in XSLT, SVG, Javascript (including E4X)

The tools above are free forever, they are not trial period items.

You might also look Oxygen, a worthwhile tool to have. You might also have a look at XML SPY.

* A decade ago I wrote an error-correcting XML parser using SAX, to read SEC documents some of which were 'broken' in various ways, including being not valid xml documents, having content occurring in sections where they are not supposed to be, having data that was expressed by other than what the schema said it should be. Kay's SAXON XSLT includes the capability for users to write their own parser eventhandlers (in Java). That means you can do things with SAXON XSLT where other XSLT systems using Schemas either reject a file or throw up their hands in incompetance. Is your (input) Geo-data always 100% perfect?

Note: There are Copyright / IP Rights associated with the following material.
Unless an item specifically says in it that it is PUBLIC DOMAIN all the items are NOT PUBLIC DOMAIN.

Google Maps source

GML Specification Doc

GML Schemas

KML Specification Doc

KML Example Data Set

NASA JPL SWEET biosphere.owl

NASA JPL SWEET data.owl

NASA JPL SWEET earthrealm.owl

NASA JPL SWEET human_activities.owl

NASA JPL SWEET material_thing.owl

NASA JPL SWEET numerics.owl

NASA JPL SWEET phenomena.owl

NASA JPL SWEET process.owl

NASA JPL SWEET property.owl

NASA JPL SWEET space.owl

NASA JPL SWEET substance.owl

NASA JPL SWEET sunrealm.owl

NASA JPL SWEET time.owl

NASA JPL SWEET units.owl

Countries example ontology

family.swrl.owl example ontology

drexel.edu1 example ontology

drexel.edu2 example ontology

ogc-gml example ontology

travel.owl example ontology

OWLviz download

The new javascript programs in Ontoclock are stubs used to provide an example display when the SVG file is opened in Firefox 3.
The stub code will be elaborated at a later date.

The code which does the metaprogramming-based discovery of causal links in the SVG programs is not shown or available at this time.

press the button

NE_States.pdf

NE_States.svg

barchartOSG.svg

KcgShotCG.png

OntoClock1.svg

OntoClock2.svg

SiemensClock-512X512.png

David's Barchart, .jpg, of SVG output

The XML Schema for the schools.xmlfile is next, below. These both were example OGC files which have since disappeared from the web. The school.xml file I use has some embellishments (added to its end) which did not appear in the original. It should be quite obvious just by looking at the file what the additions are.

press the button

schools.xsd

If you want to understand what the parts of a SWRL document are / look like have a look at swrlx.xsd.xml using Oxygen or Notepad++.
This XSD schema shows all the parts of SWRL so that you can see what SWRL rules are constituted of. You can define and 'run' SWRL rules using Protege, with the SWRL-plugin. By downloading the "FULL" version of Protege (above) you get a collection of very useful plugins in addition to Protege itself. Protege is a free download from Stanford (above).

swrlx.xsd.xml

Protege/OWL running a SPARQL query on Periodic Table ontology

SVGprog01.xsl is an XSL program that I wrote for an Extreme Markup Language 2004 conference presentation. It used 1999/XSL/Transform, exslt.org/dates-and-times" extension-element-prefixes="date". The purpose of the program was to perform programmatic analysis of the SVG program it was initiated from and print a findings report describing what (SVG) things (ie code) was found. A similar version of the XSL program was used elsewhere. This program is used as a front-end of a program-discovery system which can locate KML Marker code in KML data sets and translate those into SVG, or vice-versa. Examples of (translated and source) KML data sets and SVG data sets were shown and can be found on this page. It should be noted that XSLT can be used to translate a KML extrusion file, such as the one included on this page into SVG 2 1/2 D [or 3D] (SVG is officially a 2D system, I am the author of the SVG metadata element). XSLT or Javascript can also generate X3D instead of SVG or as well.

SVGprog01.xsl

The DewPoint Algorithm XML file is a MathML file which shows how the mathematical calculation which performs finding the Dew Point is constituted. The point of this example is that MathML is an XML namespace, that it represents mathematical equations / formulas in both appearance form and in meaning or semantic form. Latex and other software can capture how math should be depicted or drawn but they can not show the meaning or semantics of the math, any more than MS Word can capture the meaning / semantics of the text it describes how to display. By associating the semantic terms for the various sub-parts of an equation represented in MathML with ontologies, such as NASA JPL's SWEET numerics.owl ontology, the computer is able to represent and "have" the meaning / implication of the equation / formula. Programmatically-based Curve-fitting knowledge can be applied to understanding both the nature of the mathematical interrelationship between constituents of the curve but also the import or "meaning" of the curve in addition to merely its "fit" (which is an equation).

DewPoint_Algorithm.xml

There will be a brief (perhaps 3 minute long) podcast file associated with this set of XSLT programs to explain the point of including them.
The section about SAXON XSLT (titled SAXON XSLT) can be easily read without listening to the the podcast first.
SAXON XSLT is Java oriented and so it is possible to extend SAXON XSLT by means of using Java functionality, such as:
{xsl:value-of select="math:sqrt($arg)"
xmlns:math="java:java.lang.Math"/}

This will invoke the static method java.lang.Math.sqrt()

XSLTcookbkLongws.txt

SVG barchart program, download this SVG program and open it inside Firefox 3 or any SVG competent program and see the barchart. If one looks at the SVG program itself one sees that there is a substantial amount of metadata content in this barchart program's SVG metadata element. That metadata was explicitly inserted in the SVG source code but it could be ommitted and derived programmatically. See the next item after this one for details (barchartxsl.xml).

barchart.svg

If one opens this file in Firefox 3 (or inside of any XML/XSLT program) the program-analyzing XSLT program runs and prints a report of the SVG code content there. Looking at this report one can see it wouldnt take too much additional XSLT code to perform additional analysis: such as using the x,y SVG object locations to generate metadata RDF predicates such as those seen in the SVG metadata element content of the SVG barchart program. (Javascript could be used to do these things too.) That RDF looks like:
(rdf:Description about="#bar1")
(omcsvg:AtRight resource="#bar2"/)
(/rdf:Description)

and:
(rdf:Description about="#text1")
(omcsvg:IsNear resource="#xbaseline"/)
(/rdf:Description)

barchartxsl.xml

Of course Javascript or XSLT could be used to analyze XML files consisting of the above RDF predicate assertions and locate any logical patterns, such as the collection of parallel coloured bars, with date-text and other text below them; and detect that such a logical pattern of spatial-relationship RDF predicates describes a 'barchart' (illustration). Also, have a look at statistical-graph-complex.xml and igraph-example2.xml (both below) to see ontological use of similar ideas.

SWOOP space.owl ontology .jpg

Person.owl and Driver.owl are example (small) ontologies which allows one to examine them by eye, using Firefox 3 or Oxygen, or a simple text editor (not Word), and see that Person.owl is about Person drives Car, and that Driver.owl is about Driver drives Car. Many humans, who are incredibly sloppy in their useage of terms might somewhat equate the two ontologies as talking about basically the same thing. If one takes Person from Person.owl and melds that definition into Driver.owl without precautions he finds that undesireable things have been "inherited". An audio podcast will be posted to this website area which basically explans the salient points of this example (using these two ontologies). It is worthwhile to download both ontologies, they are small files.

press the button

Driver.owl.xml

Person.owl.xml

Humans.owl.xml

graphWidgetExample 1, defining an ontology visually / graphically

graphWidgetExample 2, defining an ontology visually / graphically

SensorML uses definitions, such as 'property', ontology, dictionary semantics

myfooBarchart.pdf is a PDF file of myfooBarchart (PDF used to prevent collapsing of space, indentation etc) A brief podcast will be associated with this PDF explaining the various details inside the file. Briefly, this SVG file contains an SVG DESCription element which uses the myfoo namespace to provide a scene-graph as a DESCription of the SVG illustration. The SVG metadata element contains the RDF spatial-relationship predicates discussed above.

myfooBarchart.pdf

Notice that there is a travel ontology (above) from Stanford which is meant to be used by newbies to ontologies as a learning tool. It, purposely, is not as complete as it could be to provide coverage sufficient for use in a commercial on the web endeavour. It was never meant for that purpose. The travel ontology below next is quite extensive and attempts to incorporate concepts from the OTA travel industry schema sets.

travelontology.owl

This ontology from dumontierlabs provides specific knowledge about (data) graphs, xy graphs, barcharts and such graphs. It provides knowledge specific to that domain which the NASA JPL space.owl ontology does not have, because the latter is designed for the context of general space, not just the space domain subset of data graphs. As such this ontology (next) is very useful in reasoning about graphs by augmenting the NASA JPL space.owl ontology, where it does not posess the detailed subdomain knowledge (about data graphs).

statistical-graph-complex.xml

This XML data set, sweCurve.xml, is from OGC SensorML documentation and it can be understood by the computer by programmatic analysis of the data set sweCurve.xml by analysis programs which use a reasoner and the knowledge in statistical-graph-complex.xml (above) and numerics.owl (above).

sweCurve.xml

Notice that there is an ontology of time already available (above). It is the time.owl ontology in the NASA JPL SWEET collection of ontologies (above). This ontology (below, next), from dumontierlabs, was designed to depict a different aspect of time domain than in the time.owl time ontology of SWEET. This time ontology is made available to you so that you might compare the different aspects or facets of time as depicted in each of these two ontologies. [A third ontology about time will be available for download elsewhere on this page, it uses the DAML representation.}

time-interval-primitive.xml

This example ontology from dumontierlabs is of interest for several reasons:
a) it contains data (points) values defined in the ontology itself. While rather verbose it is one way to specify data values for series data sets,
b) this example ontology has a few xy-graph specific graph-knowledge items of interest which allow the ontology to deal with such things as "slope" and graph-data "steps". It also has defined in it a few useful xy-graph semantic notions such as "start-point" and "end-point".
c) the semantics of a particular (data) instance of an xy-graph are captured / depicted in this example ontology, and this means that a natural-language interface may be coupled with a (DL) reasoner program such that one might type questions about the graph, have the reasoner reason about the graph, and output an (typed) English response. [A text-to-speech system might be used to speak that output text for a disabled person.]

igraph-example2.xml

Time.daml, notice that it is a different conceptualization of time compared with time.owl. The three versions of time ontologies shown on this page is to show that ontologies 'about' some domain are created using a particular context, what we call 'point of view' POV. Notions of truth and beauty depend on 'where you are coming from', this is POV. Intentionality is used to express POV, often towards 'purpose'. (Intentionality is dealt with via OASIS HUML.)

time.daml

The data files are text (XML, RDF, RDFS, OWL), so if you cant download Notepad++ you might use
Microsoft Notepad on a Windows machine to look at the files
Kate (or Emacs, VI, Teco) on a Linux machine to look at the files
the equivalent program on a MAC to look at the files

Get Firefox 3, it does decent autospacing and colouring for you with XML-type files and has a built-in parser.
It can display SVG files, including SVG animated ones. It can run XSLT stylesheets, including those which can translate an XML data file into an SVG illustration, or either of these into a KML file. The KML file would be viewed with Google Earth. Firefox 3 can display (so-called) 3D files like X3D, VRML, KML. Firefox 3 works nicely with the DOM (Document Object Model) and FF3's Javascript (EcmaScript) includes E4X which speeds up XML file processing. [E4X uses object technology to represent text-based XML.]

open-meta.com

GeoWeb Page

GeoWeb 2008

This page generated with Nvu