25.07.2013 Views

January 2012 Volume 15 Number 1 - Educational Technology ...

January 2012 Volume 15 Number 1 - Educational Technology ...

January 2012 Volume 15 Number 1 - Educational Technology ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

if x include with y, and y include with z then x include with z.<br />

Rule expression<br />

if include(x, y) and include(y, z) then include(x, z)<br />

Constraint 4. inverse property<br />

OWL expression<br />

<br />

<br />

<br />

<br />

<br />

Semantic meaning<br />

There is an inverse relation between application and standard.<br />

Rule expression<br />

if application (x, y) then standard(y, x)<br />

XML-based RuleML Logic Program<br />

The RuleML data model can represent Horn clause rules. An OWL class is treated as a unary predicate. An OWL<br />

property is treated as a binary predicate. Assertions about instances in a class are treated as rule atoms (e.g., facts) in<br />

which the class predicate appears. Assertions about property links between class instances are treated as rule atoms<br />

in which the property predicate appears. RuleML allows a predicate symbol to be a URI; this capability is used<br />

significantly herein, since the names of OWL classes are URIs.<br />

Example 4 presents a RuleML rule for the non-monotonic rule that shows in the rule layer of Figure 1. This rule<br />

requires the representation of complex implications, a capability that goes beyond the simple implications available<br />

in OWL. This example indicates that RuleML not only provides a general implication in the form of Horn clauses,<br />

but also that its XML representation makes it the ideal choice for use with OWL. The SoPro ontology is defined in<br />

the previous section, and all its classes and properties are available to be used as elements in the rule. The RuleML<br />

rules file consists of only the LOFinder rulebase.<br />

Example 4.<br />

RuleML expression<br />

<br />

<br />

treeModeXML DOM<br />

<br />

<br />

XMLParserXMLJAXP<br />

usingJAXPDOM<br />

<br />

Rule expression<br />

if XMLParser(XML, JAXP) and using(JAXP, DOM)<br />

then treeMode(XML, DOM)<br />

Inference meaning<br />

If an XML course adopts a JAXP parser that is developed by DOM then the XML course adopts DOM method to<br />

extract data.<br />

LOM Metadata<br />

The software domain in the example represents all learning objects as HTML documents. The following discussion<br />

illustrates how LOM can be used to annotate relationships of learning objects using the concrete examples in the<br />

306

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!