Comments on: Not another mapping markup language! http://aabs.wordpress.com/2008/08/27/not-another-mapping-markup-language/ Stay the curse Mon, 02 Nov 2009 21:34:17 +0000 http://wordpress.com/ hourly 1 By: Stephen http://aabs.wordpress.com/2008/08/27/not-another-mapping-markup-language/#comment-21031 Stephen Tue, 17 Feb 2009 22:34:12 +0000 http://aabs.wordpress.com/?p=566#comment-21031 Have you looked at SWRL [1] as a mapping language. I've used it fairly sucessfully for this purpose. The Protege project uses JESS as the rule execution engine [2]. [1] http://www.w3.org/Submission/SWRL/ [2] http://protege.cim3.net/cgi-bin/wiki.pl?SWRLJessTab Have you looked at SWRL [1] as a mapping language. I’ve used it fairly sucessfully for this purpose. The Protege project uses JESS as the rule execution engine [2].

[1] http://www.w3.org/Submission/SWRL/
[2] http://protege.cim3.net/cgi-bin/wiki.pl?SWRLJessTab

]]> By: Nodalities » Blog Archive » This Week’s Semantic Web http://aabs.wordpress.com/2008/08/27/not-another-mapping-markup-language/#comment-20871 Nodalities » Blog Archive » This Week’s Semantic Web Mon, 01 Sep 2008 22:17:17 +0000 http://aabs.wordpress.com/?p=566#comment-20871 [...] Not another mapping markup language! [...] [...] Not another mapping markup language! [...]

]]> By: Kingsley Idehen http://aabs.wordpress.com/2008/08/27/not-another-mapping-markup-language/#comment-20868 Kingsley Idehen Sun, 31 Aug 2008 17:00:22 +0000 http://aabs.wordpress.com/?p=566#comment-20868 My reasons for reversing the order are actualy quite historic. Enterprise Object Frameworks (EOF) from NeXT (now part of Apple) was one of the earliest attempts of Object and Relational DBMS realm meshing, the goal was to create a "Concrete Conceptual Model" as the focal point of the MVC pattern to which EOF was bound courtesy of its proximity to Objective-C. Unfortunately, as the concepts of EOF spread into the broader market, the focus on Objects and then to RDBMS storage, due to expressivity power from the Object side dominated technology evolution. OWL, RDFS, and RDF collectively provide technology that now enable us to step back and invert the model such that we leverage the expressivity of OWL (in particular) when constructing "Concrete Conceptual Models" from existing data that resides in RDBMS engines. If you are able to take a close look at Virtuoso and its SPASQL (SPARQL inside SQL) based Meta Schema Language, you will see that we provide very deep and poweful expressivity as a natural component of the Mapping language. We want to work with rich data objects that are inter-connected via HTTP (the Web) and by doing so we arrive back at EOF (or more recently Entity Frameworks from Microsoft) without platform lock-in at the OS, programming language, framewok, or DBMS levels. Links: 1. http://virtuoso.openlinksw.com/presentations/Virtuoso_RDF_Views/Virtuoso_RDF_Views_1.html Note: if you get the OpenLink Data Explorer (http://ode.openlinksw.com) for Firefox and look at the presentation above (or other Web information resources) you will also see where I am coming from with additional clarity re. Web as the new "Concrete Conceptual Model" substrate for interlinked data objects (Linked Data). LINQ and what I am trying to unveil are one of the most potent technology combos the industry has seen in a long time (since EOF which was powerful albeit land locked. Remember the Web was invented on a NeXT black box). My reasons for reversing the order are actualy quite historic. Enterprise Object Frameworks (EOF) from NeXT (now part of Apple) was one of the earliest attempts of Object and Relational DBMS realm meshing, the goal was to create a “Concrete Conceptual Model” as the focal point of the MVC pattern to which EOF was bound courtesy of its proximity to Objective-C.

Unfortunately, as the concepts of EOF spread into the broader market, the focus on Objects and then to RDBMS storage, due to expressivity power from the Object side dominated technology evolution.

OWL, RDFS, and RDF collectively provide technology that now enable us to step back and invert the model such that we leverage the expressivity of OWL (in particular) when constructing “Concrete Conceptual Models” from existing data that resides in RDBMS engines.

If you are able to take a close look at Virtuoso and its SPASQL (SPARQL inside SQL) based Meta Schema Language, you will see that we provide very deep and poweful expressivity as a natural component of the Mapping language.

We want to work with rich data objects that are inter-connected via HTTP (the Web) and by doing so we arrive back at EOF (or more recently Entity Frameworks from Microsoft) without platform lock-in at the OS, programming language, framewok, or DBMS levels.

Links:
1. http://virtuoso.openlinksw.com/presentations/Virtuoso_RDF_Views/Virtuoso_RDF_Views_1.html

Note: if you get the OpenLink Data Explorer (http://ode.openlinksw.com) for Firefox and look at the presentation above (or other Web information resources) you will also see where I am coming from with additional clarity re. Web as the new “Concrete Conceptual Model” substrate for interlinked data objects (Linked Data).

LINQ and what I am trying to unveil are one of the most potent technology combos the industry has seen in a long time (since EOF which was powerful albeit land locked. Remember the Web was invented on a NeXT black box).

]]>