CS 6975 Web Semantics Normalizers for RuleML 1.0 in XSLT 2.0 Nada Alsalmi ‍ Leah Bidlake ‍ Ao Cheng ‍ Thea Gegenberg ‍ Emily Wilson Instructor: Dr. Harold Boley Advisor: Dr. Tara Athan

Overview Introduction Comparison to previous Normalizer Our 4-Phase Normalizer: ▫Phase 1 – Adding Role Tags ▫Phase 2 – Canonical Ordering ▫Phase 3 – Making attribute default values explicit ▫Phase 4 – Pretty Print Demo

Introduction Work Flow diagram:

Multiple Phases within a Single Stylesheet Within a single stylesheet, a pipeline is expressed as a series of variables:

Comparison to Derek’s & David’s Normalizer Performed transformation in 1 Pass/Phase … …

PHASE 1

RuleML 0.91 to 1.0 All references for namespace and schema locations changed to: Output from style sheet has RuleML Version 1.0 as default namespace.

RuleML 0.91 to 1.0 Changes to names of role tags: Children of ▫Role tag replaced with ▫Role tag replace with Children of ▫Role tag replaced with ▫Role tag replace with Name of interpretation attribute: changed

RuleML 0.91 to 1.0 – Other Changes Webizing attribute: changed Name of type tag for unified term: ▫ changed to Name of type tag for constant term: ▫ changed to Content of ▫Role tag wraps all content of

Phase 1 – Add Missing Edge Stripes Edge is also referred to as role tag or method tag. Match the elements using the parent tag. Determine if the children were already wrapped with the appropriate tag. Wrap the ‘naked’ children with the appropriate role tag. For some elements an index attribute was also added.

Phase 1 Each time an element was matched there was a test to determine if the role tags were already present for any or all of the children. In some cases the children may already be wrapped in role tags but in a different order, which had to be tested for. Test cases developed including: relaxed, partially normalized and fully normalized.

Phase 1 Adding missing stripes to Implies and Entails – difficult because of the number of possibilities of missing, stripes. As suggested by Tara Athan, our advisor, this was simplified by assuming that the and are in canonical position already if stripes are skipped.

Phase 1 – Example 1 st child wrapped with 2 nd child wrapped with Check for partially normalized: ▫If the 1 st child was already wrapped with then the 2 nd child has to be wrapped with

Phase 1: Example

Test CaseResults Relaxed:Normalized:

Test CaseResults Partially Normalized:Normalized:

Test CaseResults Partially Normalized:Normalized:

Test CaseResults Fully Normalized:Normalized:

PHASE 2 Canonical Ordering

Phases 2: Canonical Order Output Schema used to infer canonical ordering e.g.

Phase 2: Example

Phase 2: Example (cont.)

Phase 2: Example

Phase 2: Example (cont.) Before normalization: After normalization:

PHASE 3 Default Values  Treatment of attributes with default values  Remain the original instinct of input

Modes Phase 1, Phase2, Phase3 are independently implemented. Use the feature of “mode” from XSLT 2.0  Format the same Data differently in different Places  XSLT Element

Default ( yes | no ( yes | no bidirectional | forward | backward bidirectional | forward | backward ( no | yes ( 0.. | 1 ( no | yes ) List

Problems Then oxygen seemed to automatically put in all possible attributes listed with their default values. If list all the schemas in the ruleml file, i.e. Oxygen explicit copying of default attributes won’t happen if you do delete the attributes of the RuleML tag that specify the schema.

Results Ruleml File After normalized:

PHASE 4 Pretty Print

Pretty Print Output RuleML nicely Comments For some tags we don’t want a new line

Pretty Print – How? Variables and params ▫

Pretty Print – Outline

Final Demo Normalizer: u.unbf.ca/~lbidlak1/100relaxed-to-normal.xslt u.unbf.ca/~lbidlak1/100relaxed-to-normal.xslt Handout Website: u.unbf.ca/~lbidlak1/ u.unbf.ca/~lbidlak1/