Welcome to the Open Data Web

This is typical Internet open data web page; everyone can easily publish pages like this using any good word processor. Pages like this can be used to publish any sort of practical meaning as data, and publishing data in this way provides an automatic 100X searching and sharing advantage over other alternatives.

This page is a standard web document (HTML) page with some hyperlinked data sections. Every data page needs to define a unique Internet publishing space known as a namespace. The first hyperlinked data section of this page is:

1.  Space: Example Space 1

1.1.  Self: http://example.com/example space 1

 

This is a data section with two statements; it,s the one sort of section that appears first one every data web page. The Space, statement names the data space for this page and the Self, statement assigns a unique Internet namespace identifier for this space. This name starts with a domain name and continues with one or more levels of additional hierarchical names. The owner of the domain must choose a hierarchical structure of namespace names. This structured naming approach conforms to the World Wide Web Consortium XML Information Set recommendation.

What does this data page mean? Let's start with a simple declaration:

1.  Declaration: Barak Obama Person

1.1.  Synopsis: Person @ Primitives

1.2.  Synopsis: Individual @ Instrumentality

1.3.  Social Profile @ Basics: B. Obama Facebook Profile

 

This declaration tells us that Barak Obama is an individual person and provides a hyperlink to his social profile on Facebook.com. The statements with name Synopsis, are references to principles provided by the StateWare Synopsis publishing foundation framework. The value Person @ Primitives, refers to the principle Person, in the Synopsis perspective Primitives.Note that there are lots of hyperlilnks in the declaration, every hyperlilnk resuses information and adds to the referential richness of the data web.

Now let's declare the city of Washington, D.C.

1.  Declaration: Washington D.C. USA Place

1.1.  Wikipedia @ Basics: Wikipedia Washington D.C.

1.2.  Synopsis: Place @ Primitives

 

Now we can combine these to express the simple meaning of presence:

1.  Presence @ Primitives: State of The Union 2011 Presence

1.1.  Person @ Primitives: Barak Obama Person

1.2.  Place @ Primitives: Washington D.C. USA Place

1.3.  Period @ Primitives: 2011-01-25-04:00Z

 

This tells us the Barak Obama was present in Washington D.C. on January 25, 2011 EST, the date of the 2011 State of the Union Address.

Next let,s declare a practice:

1.  Declaration: State of the Union Address Practice

1.1.  Wikipedia @ Basics: Wikipedia State of the Union

1.2.  Synopsis: Address @ Argument

1.3.  Synopsis: Assertion @ Argument

1.4.  Synopsis: Practice @ Primitives

 

Adding this practice to the previous model of presence gives us a model of practicality:

1.  Practicality @ Primitives: State of the Union 2011 Practicality

1.1.  Person @ Primitives: Barak Obama Person

1.2.  Place @ Primitives: Washington D.C. USA Place

1.3.  Period @ Primitives: 2011-01-25-04:00Z

1.4.  Practice @ Primitives: State of the Union Address Practice

 

Note that this is a dimensional model with four dimensions: Person, Place, Period, and Practice. All practical meaning is intrinsically dimensional and differential in the classical applied science approach to understanding practical information.

Now let,s add some praxeology; praxeology is the applied science mechanics of practice management. Continuing the prior example:

1.  Praxeology @ Praxeology: State of the Union 2011 Praxeology

1.1.  Plan @ Praxeology: State of the Union 2011 Practicality

1.2.  Performance @ Praxeology: State of the Union 2011 Practicality

 

This tells us the both the plan and the performance of the 2001 State of the Union are both modeled by the prior practicality example. Praxeology is a particularly useful perspective for adding meaning to practice models, and there are many other useful perspectives as well. Here,s a continuation of the prior example from the Deontology perspective:

1.  Duty @ Duty: State of the Union 2011

1.1.  Deliverable @ Duty: State of the Union 2011 Practicality

1.2.  Delivery @ Duty: State of the Union 2011 Practicality

1.3.  Deadline @ Duty: 2011-01-25-04:00Z

 

There are many convenient ways to decorate this data section. For example:

1.  Duty @ Duty: State of the Union 2011 Version 2

1.1.  Deliverable @ Duty: State of the Union 2011 Practicality

1.2.  Delivery @ Duty: State of the Union 2011 Practicality

1.3.  Deadline @ Duty: 2011-01-25-04:00Z

1.4.  Synopsis: Diligence @ Duty Values

1.5.  Synopsis: Eloquence @ Elite

1.6.  Synopsis: Clear @ Communication

 

The data page demonstrates only a tiny fraction of the power of StateWare data web modeling. The StateWare Synopsis foundation includes over 15,000 reusable, recombinant practical meaning principles. These familiar principles are the 33 publishing glue and grease required to preserve all the power, precision, and portability of your best practical prose. In routine practice a data web page may contain many thousands of sections, and a model project may invovle hundreds or thousands of data web pages.

The publishing framework for this page is provided by a highly simplified version of the StateWare Synopsis binding framework published here.