Changes between Version 3 and Version 4 of IdsAdiTemplateAxiomatizationTools

Timestamp:

11/05/09 21:55:29 (14 years ago)

Author:

jowik (IP: 193.212.132.34)

Comment:

--

IdsAdiTemplateAxiomatizationTools

@@ -44 +44 @@
 = Some reasons why we need templates =
  - Simplify use of ISO 15926 representations
-         - Expressions in the language of ISO 15926-2 tend to be
-     verbose. The entity types are also hard to grasp. With templates,
-     the logical design work can be left to modelling experts.
+         - Expressions in the language of ISO 15926-2 tend to be verbose. The entity types are also hard to grasp. With templates, the logical design work can be left to modelling experts.
  - A uniform approach to knowledge capture
-         - Templates are always ''statement forms''. Any valid template
-     instance corresponds to a statement.
+         - Templates are always ''statement forms''. Any valid template instance corresponds to a statement.
  - Simplify use of n-ary predicates 
-         - Due to its basis in standard Description Logic, OWL has only
-     unary and binary predicates
-         - Templates are a convenient way to introduce n-ary predicates,
-     without introducing too much semantic confusion (cf. W3C's
-     [http://www.w3.org/TR/swbp-n-aryRelations/#useCase3 Purchase] example, for which instances are purchases, not facts)
+         - Due to its basis in standard Description Logic, OWL has only unary and binary predicates
+         - Templates are a convenient way to introduce n-ary predicates, without introducing too much semantic confusion (cf. W3C's [http://www.w3.org/TR/swbp-n-aryRelations/#useCase3 Purchase] example, for which instances are purchases, not facts)
  - Convenient exchange of representations
-         - Templates are comparable to SQL table definitions, but the most
-     interesting roles (columns) are typed using reference data
+         - Templates are comparable to SQL table definitions, but the most interesting roles (columns) are typed using reference data
  - Convenient data transfer
          - It's easy to instantiate templates and move a payload
 
-All of the above are good, but not exactly revolutionary. Arguably,
-the greatest advantage of templates is found in the interpretation of
-template rules as logical axioms.
+All of the above are good, but not exactly revolutionary. Arguably, the greatest advantage of templates is found in the interpretation of template rules as logical axioms.
 
  - Basis in precise modelling
-         - Templates are expressed in a clearly defined limited first-order
-     logic, whose properties are well known
+         - Templates are expressed in a clearly defined limited first-order logic, whose properties are well known
  - Definitions can be tested for compliance with ISO 15926-2
          - This is much of today's topic
@@ -75 +65 @@
  - Complex templates can be defined in terms of simpler templates
  - Libraries of templates can be tested for internal consistency
- - We can check that templates are well-defined in the sense of always
-   reducing to a unique expression in the basic, Part 2 language
+ - We can check that templates are well-defined in the sense of always reducing to a unique expression in the basic, Part 2 language
 
 = Template Expander: Intro, and a minimal example =
-The
-[https://www.posccaesar.org/svn/pub/TemplateExpander/applet/template-expander.html Template Expander] is a tool for working with template design. It
-was written in Java by [http://heim.ifi.uio.no/martingi/ Martin Giese]. Development was funded by DNV
-IRM. 
+The [https://www.posccaesar.org/svn/pub/TemplateExpander/applet/template-expander.html Template Expander] is a tool for working with template design. It was written in Java by [http://heim.ifi.uio.no/martingi/ Martin Giese]. Development was funded by DNV IRM. 
 == Java library ==
-Using the Java library
-([https://www.posccaesar.org/svn/pub/TemplateExpander/cmdline/template-expander.jar template-expander.jar]), expansion of template
-rules can be built into ISO 15926 applications.
-
-The code is available as free software, with a BSD-type
-[https://www.posccaesar.org/svn/pub/TemplateExpander/LICENSE LICENSE]:
+Using the Java library ([https://www.posccaesar.org/svn/pub/TemplateExpander/cmdline/template-expander.jar template-expander.jar]), expansion of template rules can be built into ISO 15926 applications.
+
+The code is available as free software, with a BSD-type [https://www.posccaesar.org/svn/pub/TemplateExpander/LICENSE LICENSE]:
 {{{
 Copyright (c) 2009, DNV Information Risk Management 
@@ -110 +93 @@
 }}}
 == Java applet ==
-At
-[https://www.posccaesar.org/svn/pub/TemplateExpander/applet/template-expander.html Template Expander], a Java applet has been provided with a heading,
-an introduction, and IDS-ADI and DNV logos.
+At [https://www.posccaesar.org/svn/pub/TemplateExpander/applet/template-expander.html Template Expander], a Java applet has been provided with a heading, an introduction, and IDS-ADI and DNV logos.
 === Window "Template Definitions" ===
 Enter all template definitions into this window.
 
-Upon initialization, the templates defined in the
-[https://www.posccaesar.org/svn/projects/ISO15926/Part7-Apr-2009_delivery/ISO15926-7_TS.pdf Part 7 April 2009 draft] 
-are loaded here, in Prover9 format.
+Upon initialization, the templates defined in the [https://www.posccaesar.org/svn/projects/ISO15926/Part7-Apr-2009_delivery/ISO15926-7_TS.pdf Part 7 April 2009 draft] are loaded here, in Prover9 format.
 
 For a toy example, consider a two-place template "!SiblingOf(x, y)" for