Some additions, changes to the document

[Tara Athan <taraathan@gmail.com>]

1st paragraph,
Section 5.4 Node and Edge Element Dichotomy

LegalRuleML adopted, for its normalized serialization,

=>

LegalRuleML adopted, for its normalized serialization (see Section 5.6.1 Normalized Serialization),

where Node elements alternate with edge elements,

=>
where Node elements (see Section 5.4.1 Node Elements) alternate with edge elements (see Section 5.4.2 Edge Elements)

add after last line: "The striped syntax of normalized LegalRuleML is also compatible with the normalized striped syntax of RuleML, although it differs in a few particulars."

2nd paragraph
(also called type)
=>
(also called type in RuleML)

(also called role)
=>
(also called role in RuleML)

3rd paragraph

Delete: "The ruleml:slot element also corresponds to the structure of the abstract syntax, with the first child of the slot corresponding to the property of a triple and the second child corresponding to the object of the triple."

4th paragraph

The LegalRuleML compact serialization is defined in this way.

=>

The LegalRuleML compact serialization is defined in this way (see Section 5.6.2 Compact Serialization) .

5th paragraph

In the XML document tree, elements that have no children

=>

In the XML document tree of a LegalRuleML document, elements that have no children

5.4.1

We use the prefixes lrmlmm and rulemm, reps.,

=>

We use the prefixes lrmlmm and rulemm, resp.,

@@@ref
=>
http://wiki.ruleml.org/index.php/Metamodel

(heading) Classification of Node Elements
(modify) emphasize the names of Node classes as bold or italic, or perhaps we should itemize?

(following)

Every LegalRuleML Node element may optionally have a child element that attaches a comment to it, specified in an lrml:Comment element (see section @@@Annotations - Comment and Paraphrase).

(insert)
The Node elements (in the LegalRuleML and RuleML namespaces) that may contain a comment belong to the class of Commentable Node elements, which is the union of LegalRuleML Node elements and RuleML Branch or Leaf/Branch Node elements.

LegalRuleML _expression_ elements are Node elements in the LegalRuleML and RuleML namespaces that render one or more Legal Norms or a fragment of a Legal Norm. This Node class is the union of RuleML Branch or Leaf/Branch Node elements, together with the LegalRuleML Override and Reparation Nodes.   Node elements in the LegalRuleML _expression_ class may contain a paraphrase.
(end insert)

The types of RuleML Branch or Leaf/Branch Node element have been extended in the LegalRuleML syntax so that RuleML elements within a LegalRuleML document may optionally have a child element that attaches a paraphrase to it, specified in an lrml:Paraphrase element (see section @@@Comment/Paraphrase).

(insert)
Additional Node classes are Associator, Associable, Alternative, Actor, and Collector.
Associator Nodes are Node elements that can define associations - these are lrml:Context and lrml:Association.
Associable Nodes are Node elements that can participate in associations - these are lrml:Association, lrml:Strength, lrml:Temporal Characteristic(s), lrml:Authority, lrml:Jurisdiction, lrml:Source, lrml:LegalSource.
Alternative Nodes are Node elements that can belong to an Alternatives collection - these are lrml:Statement or lrml:Statements.
Actor Nodes are Node elements that can fill a Role - these are lrml:Agent and lrml:Figure.
Collector Nodes are Node elements that can contain a collection - these are lrml:LegalRuleML, the root element, lrml:(Legal)Sources, and lrml:Statements

(end insert)

A group of common optional attributes

=>
(heading) Attributes of Node Elements

A group of common optional attributes

=>

(heading) Attributes of Edge Elements

5.5

pointer to a user-defined signature

=>

pointer to a user-defined specification

ruleml:Operation   @type

ruleml:Negation    @type

ruleml:Rule        @strength, hasStrength

=>

ruleml:Operation   @type @style

ruleml:Negation    @type @style

ruleml:Rule        @strength @style, hasStrength

5.6

applying the normalizer XSLT transformation

=>

applying the normalizer XSLT transformation ( @@@ref to XSLT artifact?)

(similarly, for compactifier)

5.7

five

=>
four

delete

composite elements that are made up of different dependent parts, (e.g., a rule <Rule>  consists of an antecedent <if> and conclusion <then>).

as well as 5.7.4, as it is in conflict with the metamodel, which does not use the composite pattern

5.8.1

Example: SuborderList

=>
An example of this design pattern is lrml:SuborderList.

5.8.2  Leaf edges
LegalRuleML introduces a syntactic pattern that is not present in RuleML – the leaf edge element:
 is an edge element that is empty
always has at least one attribute, typically @keyref
=>
5.8.2  Leaf edges
LegalRuleML introduces a syntactic pattern that is not present in RuleML – the leaf edge element:
 A Leaf edge element is an edge element that is empty. These elements are required to have at least one attribute, typically @keyref .

(delete)

See stripe_leaf_module.rnc (Stripe Required, Leaf Not Obligatory
 and Stripe Optional, Leaf Not Obligatory) and stripe_required_module.rnc (Leaf Obligatory)

(end delete)

5.9 CURIES, Relative IRIs and the xsd:ID Datatype
LegalRuleML employs a variety of syntactic forms for labeling components with identifiers, and for referring to these or other identifiers. In this section, we discuss the syntactic forms that are based on the IRI system, and compare to the corresponding forms employed in RuleML.
Need overview of prefixing and abbreviation of IRIs
qualified names (<ruleml:Rule>, “xs:integer”)
xsd:ID datatype (key = “rule1”)
same-document reference (keyref = “#rule1”)
relative IRIs other than same-document reference (“../otherdoc.lrml#rule2”)
CURIEs (iri=”ex:servb/otherdoc.lrml”, keyref=”:#rule1”)
IRI (iri=”http://servb/otherdoc.lrml”)
CURIE datatype follows RDFa (@@@citation)
conflicting ID-types for attribute “key” of element “TemporalCharacteristic” from namespace “http://docs.oasis-open.org/legalruleml/ns/v1.0/”
=>
5.9 CURIES, Relative IRIs and the xsd:ID Datatype
LegalRuleML employs a variety of syntactic forms for labeling components with identifiers, and for referring to these or other identifiers. In this section, we discuss the syntactic forms that are based on the IRI system, and compare to the corresponding forms employed in RuleML.

In RuleML 1.02 elements, attribute values that are intended to be IRIs may be expressed without abbreviation or may be abbreviated using the CURIE syntax (@@@ref RDFa).

LegalRuleML has adopted the RuleML 1.02 approach to expressing IRIs, and modifies it as follows:
* CURIE prefixes are defined (only) by lrml:Prefix elements

* @key values are expressed (only) with datatype xsd:ID, the same type of values as @xml:id
* @keyref values are expressed (only) with "same-document" relative IRIs, starting with '#'

5.10 Distributed Syntax
The ... syntactic construct, and .

=>
The ... syntactic construct.

determined according to @@@
=>

determined according to @@@ref to https://www.ietf.org/rfc/rfc3986.txt

5.11 Metamodel Refinement

(see @@@RuleMLSpec)

=>

(see @@@ref to http://wiki.ruleml.org/index.php/Glossary_of_Consumer_RuleML_1.02#.40type)

5.12

Annotations - Comment and Paraphrasre

=>

Annotations - Comment and Paraphrase

(insert)

The Annotation Node elements lrml:Comment and lrml:Paraphrase may contain arbitrary well-formed XML. Both are semantically neutral - their absence, presence or content have no semantic effect on their parent element.

All Branch Node elements, in the LegalRuleML and RuleML namespaces, may optionally have one lrml:Comment child (compact serialization) or lrml:hasComment child (normalized serialization).

The lrml:Paraphrase element is restricted to the content of LegalRuleML Expressions

6.1
RuleML syntax allows such edges to be optionally skipped, resulting in its stripe-skipped serialization.

=>
In the RuleML syntax, such edges are skippable.
no edges are skipped

=>
no edge tags are skipped
all skippable edges in the document are omitted

=>
the tags of all skippable edges in the document are omitted

reconstructs the skipped edges

=>
reconstructs the skipped edge tags

***********************************

I will send changes to the rest of the document in a separate email, later.

Tara