OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalruleml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [legalruleml] Groups - Event "LegalRuleML - TC meeting Sept. 23th" added


Dear All - I have pushed some draft examples and a new Relax NG schema that validates these examples to the repository. The syntax in these examples follows the spirit of the small example we developed in the telecon, but I made some small modifications so that it fits in better to the existing syntax. Here is a snippet of the compact version

  <!-- IRIs for legal sources may be defined in a references block -->
<lrml:References refType="http://example.legalruleml.org/lrml#LegalSource";> <lrml:Reference refersTo="ref1" refID="/au/2012-05-30/C628:2012/eng@/main#sec2.2"
      refIDSystemName="AkomaNtoso2.0-2011-10"/>
  </lrml:References>

<!-- Some IRIs for legal sources are defined in legal sources blocks. -->
  <lrml:LegalSources key="ls1">
    <lrml:LegalSource key="ref2"
sameAs="ftp://ftp.cen.eu/CEN/Sectors/List/ICT/CWAs/CWA15710-2010-Metalex2.pdf"/>
  </lrml:LegalSources>

  <!-- Legal source blocks can be nested. -->
  <lrml:LegalSources>
<lrml:LegalSource key="ref8" sameAs="http://codes.lp.findlaw.com/uscode/18/I/3/47"/>
    <lrml:LegalSources key="ls3">
<!-- Legal source blocks can contain legal sources defined in a reference block. -->
      <lrml:hasLegalSource keyref="#ref1"/>
    </lrml:LegalSources>
  </lrml:LegalSources>

<!-- A block of alternatives can be defined independent of a context, but it is not
          asserted until it is applied within some context. -->
  <lrml:Alternatives key="alt1">
    <lrml:fromLegalSources>
      <lrml:LegalSources>
        <lrml:hasLegalSource keyref="#ref1"/>
        <lrml:hasLegalSources keyref="#ls1"/>
        <lrml:hasLegalSource keyref="#ref8"/>
      </lrml:LegalSources>
    </lrml:fromLegalSources>
    <lrml:hasAlternative keyref="#ps1"/>
    <lrml:hasAlternative keyref="#cs2"/>
  </lrml:Alternatives>


  <lrml:Context key="ruleInfo1">
<!-- A context can define and apply zero to many alternatives blocks. -->
    <lrml:appliesAlternatives>
      <lrml:Alternatives key="alt2">
        <lrml:fromLegalSources>
          <lrml:LegalSources key="ls1">
            <lrml:hasLegalSource keyref="#ref1"/>
            <lrml:hasLegalSources keyref="#ls1"/>
            <lrml:hasLegalSource keyref="#ref8"/>
          </lrml:LegalSources>
        </lrml:fromLegalSources>
        <lrml:hasAlternative keyref="#ps1"/>
        <lrml:hasAlternative keyref="#cs2"/>
      </lrml:Alternatives>
    </lrml:appliesAlternatives>
<!-- When an alternatives block is applied within a context, it is not necessary to use the "toTarget" edge element. Such a context does not generate a ruleml:Rule, but establishes constraints that may apply to a ruleml:Rulebase generated by
         other contexts.-->
  </lrml:Context>

  <lrml:Context key="ruleInfo2">
    <!-- A context can apply alternatives blocks defined elsewhere. -->
    <lrml:appliesAlternatives keyref="#alt1"/>
    <lrml:appliesAlternatives keyref="#alt2"/>
  </lrml:Context>

  <lrml:Context key="ruleInfo3">
    <!-- A context can apply associations and alternatives simultaneously.
         The schema requires the Associations to be listed first.-->
    <lrml:appliesAssociations keyref="#assoc1"/>
    <lrml:appliesAlternatives keyref="#alt2"/>
  </lrml:Context>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]