Examples of Rule

• OntoUML.URML.Rule
  A representation of the model object 'Rule'.

  The following features are supported:

  • {@link OntoUML.URML.Rule#getCondition Condition}

  @see OntoUML.URML.URMLPackage#getRule() @model abstract="true" @generated
• aima.core.agent.impl.aprog.simplerule.Rule
  A simple implementation of a "condition-action rule". @author Ciaran O'Reilly @author Mike Stampone
• alt.jiapi.Rule
  Implements a Rule in an InstrumentationDescriptor. Rules determine if a given class matches a certain InstrumentationDescriptor.

  Rules can have wildcards.

  Rules are ordered according to their precedence. @author Mika Riekkinen @author Joni Suominen @version $Revision: 1.16 $ $Date: 2004/03/02 07:37:11 $

• ariba.ui.meta.core.Rule
  A Rule defines a map of properties that should apply in the event that a set of Selectors are matched. Given a rule base (Meta) and a set of asserted values (Context) a list of matching rules can be computed (by matching their selectors against the values) and by successively (in rank / priority order) applying (merging) their property maps a set of effective properties can be computed.
• br.com.caelum.vraptor.panettone.parser.rule.Rule
• br.com.six2six.fixturefactory.Rule
• ca.uhn.hl7v2.validation.Rule

  A testable rule to which HL7 messages (at least certain specific message) should conform. This is the central interface of the new HAPI validation model (as of HAPI 0.4). Previously, the only run-time message validation HAPI performs is within the setValue() methods of the Primitive datatype classes. For example when you called setValue() on a DT an exception was thrown if the String arg was not in the correct DT format. This method served well initially but left us with the following limitations:

  1. Sometimes validation is inappropriate (e.g. some of the standard rules, like phone number format, don't make sense in some regions).
  2. Couldn't add further optional constraints (such as all timestamps must have a time zone).
  3. Couldn't turn off validation to improve performance.
  4. Other forms of validation (e.g. conformance profiles, standard DTDs) were not covered.

  Thus the new validation model is broader in scope, and is based on validation rules implemented as Rule objects, which can be configured to run or not, as needed, depending on run-time configuration.

  There are three kinds of rules:

  1. PrimitiveTypeRule: Called when the values of simple datatypes are set, like the existing hard-coded datatype validations (e.g. TNFollowsNorthAmericanFormat).
  2. MessageRule: Called when complete message content is to be checked on a parsed message (e.g. conformance profile).
  3. EncodingRule: Applied to an encoded message (e.g. validation against a 2.xml Schema, a rule that prohibits empty tags, etc.).

  @author Bryan Tripp
• cbg.editor.jedit.Rule
• ch.ethz.iks.slp.impl.attr.gen.Rule
• ch.hortis.sonar.model.Rule
• ch.pollet.jzic.timezone.Rule
  @author Christophe Pollet
• client.net.sf.saxon.ce.trans.Rule
  Rule: a template rule, or a strip-space rule used to support the implementation
• com.amazonaws.services.s3.model.BucketLifecycleConfiguration.Rule
  S3 HTTP response handler that knows how to pull S3 object content and metadata out of an HTTP response and unmarshall it into an S3Object object.
• com.axemblr.provisionr.api.network.Rule
• com.buschmais.jqassistant.core.analysis.api.rule.Rule
  Interface for all rules.
• com.clarkparsia.pellet.rules.model.Rule
  larkparsia.com>

  @author Ron Alford
• com.clarkparsia.pellet.rules.rete.Rule
  larkparsia.com>

• com.codeforces.graygoose.model.Rule
• com.cosmo.ui.templates.Rule
  Representa una regla de aplicaci�n de plantillas. @author Gerard Llort
• com.dianping.cat.home.rule.entity.Rule
• com.eclipsesource.tabris.passepartout.Rule

  A {@link Rule} can be compared to a CSS media query and it's content. In CSS media queries you define a condition anda block that will be active when this query becomes active. With a {@link Rule} it's the same. You define{@link Condition}s and instead of a block you will define {@link Instruction}s.

  A {@link Rule} is used everywhere in Passe-Partout. You work with them when using {@link FluidGridLayout}, {@link QueryListener} or responsive {@link Resource}s.

  @see Condition @see Instruction @noimplement This interface is not intended to be implemented by clients. @since 0.9
• com.founder.fix.bpmn2extensions.sqlmappingconfig.Rule
  A representation of the model object 'Rule'.

  The following features are supported:

  • {@link com.founder.fix.bpmn2extensions.sqlmappingconfig.Rule#getId Id}
  • {@link com.founder.fix.bpmn2extensions.sqlmappingconfig.Rule#getParameterType Parameter Type}
  • {@link com.founder.fix.bpmn2extensions.sqlmappingconfig.Rule#getSqlValue Sql Value}
  • {@link com.founder.fix.bpmn2extensions.sqlmappingconfig.Rule#getRemark Remark}
  • {@link com.founder.fix.bpmn2extensions.sqlmappingconfig.Rule#getClassPath Class Path}

  @see com.founder.fix.bpmn2extensions.sqlmappingconfig.SqlmappingconfigPackage#getRule() @model extendedMetaData="name='rule'" @generated
• com.github.jknack.antlr4ide.lang.Rule
• com.google.caja.parser.quasiliteral.Rule
  A rewriting rule supplied by a subclass.
• com.google.gwt.dev.cfg.Rule
  Abstract base class for various kinds of deferred binding rules.
• com.google.javascript.jscomp.CheckConformance.Rule
• com.hp.hpl.jena.reasoner.rulesys.Rule
  Representation of a generic inference rule.

  This represents the rule specification but most engines will compile this specification into an abstract machine or processing graph.

  The rule specification comprises a list of antecendents (body) and a list of consequents (head). If there is more than one consequent then a backchainer should regard this as a shorthand for several rules, all with the same body but with a singleton head.

  Each element in the head or body can be a TriplePattern, a Functor or a Rule. A TriplePattern is just a triple of Nodes but the Nodes can represent variables, wildcards and embedded functors - as well as constant uri or literal graph nodes. A functor comprises a functor name and a list of arguments. The arguments are Nodes of any type except functor nodes (there is no functor nesting). The functor name can be mapped into a registered java class that implements its semantics. Functors play three roles - in heads they represent actions (procedural attachement); in bodies they represent builtin predicates; in TriplePatterns they represent embedded structured literals that are used to cache matched subgraphs such as restriction specifications.

  The equality contract for rules is that two rules are equal if each of terms (ClauseEntry objects) are equals and they have the same name, if any.

  We include a trivial, recursive descent parser but this is just there to allow rules to be embedded in code. External rule syntax based on N3 and RDF could be developed. The embedded syntax supports rules such as: [ (?C rdf:type *), guard(?C, ?P) -> (?c rb:restriction some(?P, ?D)) ].
[ (?s owl:foo ?p) -> [ (?s owl:bar ?a) -> (?s ?p ?a) ] ].
[name: (?s owl:foo ?p) -> (?s ?p ?a)].
  only built in namespaces are recognized as such, * is a wildcard node, ?c is a variable, name(node ... node) is a functor, (node node node) is a triple pattern, [..] is an embedded rule, commas are ignore and can be freely used as separators. Functor names may not end in ':'.

• com.litecoding.smali2java.parser.Rule
• com.netflix.simianarmy.janitor.Rule
  The rule implementing a logic to decide if a resource should be considered as a candidate of cleanup.
• com.salas.bb.views.stylesheets.domain.Rule
  Single style sheet rule.
• com.santiagolizardo.beobachter.beans.Rule
• com.sun.xacml.Rule
  Represents the RuleType XACML type. This has a target for matching, and encapsulates the condition and all sub-operations that make up the heart of most policies. @since 1.0 @author Seth ProctorAdding generic type support by Christian Mueller (geotools)
• com.taobao.top.analysis.statistics.data.Rule
  配置信息的传输对象，用于master向slave传输配置信息 @author fangweng
• com.tonicsystems.jarjar.Rule
• com.volantis.mcs.build.themes.definitions.Rule
• com.volantis.mcs.themes.Rule
• com.webobjects.directtoweb.Rule
• eas.math.fundamentalAlgorithms.graphBased.algorithms.type0grammars.Rule
  @author Lukas König
• flash.css.Rule
  This class represents an individual rule in a CSS ruleset. @author Paul Reilly
• fri.patterns.interpreter.parsergenerator.syntax.Rule
  A rule is a list of String symbols on the right side and a nonterminal on the left side: "a ::= b c d;" A nonterminal is represented as a String with no quotes, every terminal must appear quoted by " or ' or ` (backquote). @author (c) 2004 Fritz Ritzberger
• gov.nist.scap.xccdf.document.Rule
• heart.xtt.Rule
• ign.middleman.helpers.Rule
  Created by IntelliJ IDEA. User: kgupta Date: Oct 7, 2010
• io.fabric8.service.jclouds.firewall.Rule
• javax.rules.admin.Rule
• jmathexpr.util.rule.Rule
  Represents a mathematical property, law or rule. Example: the distributive law. The general client side usage of a class implementing this interface looks as follows: Expression expr = ...; Rule = new ...; if (expr.isApplicable(rule)) expr = rule.apply(); @author Elemér Furka
• joshua.decoder.ff.tm.Rule
  This class define the interface for Rule. Normally, the feature score in the rule should be *cost* (i.e., -LogP), so that the feature weight should be positive. @author Zhifei Li, @version $LastChangedDate: 2010-01-23 11:15:03 -0600 (Sat, 23 Jan 2010) $
• joshua.discriminative.syntax_reorder.HashtableBasedHieroGrammarScorer.Rule
• lupos.rif.model.Rule
• modTransf.engine.Rule
  A rule
• model.tools.firewall.Rule
• models.Rule
  A sorting rule that allows files to be moved to a specified location when certain criteria are met. @author mustpax @author syyang
• net.sf.lapg.api.Rule
• net.sf.saxon.trans.Rule
  Rule: a template rule, or a strip-space rule used to support the implementation
• net.sourceforge.jFuzzyLogic.rule.Rule
  Fuzzy rule Rule: If (x1 is termX1) AND (x2 is termX2) .... Then (y1 is termY1) AND (y2 is termY2) [weight: 1.0] Notes: - "If" clause is called "antecedent" - "then" clause is called "consequent" - There may be 1 or more antecedents connected using a 'RuleConnectionMethod' (e.g. AND, OR) - As there are many ways to implement 'AND' and 'OR' connectors, you can customize them @author pcingola@users.sourceforge.net
• net.sourceforge.segment.srx.Rule
  Represents break or exception rule. Contains after break and before break patterns, @author loomchild
• net.sourceforge.temply.base.rules.Rule
  @author Enrico Benedetti
• org.adamtacy.client.ui.effects.impl.css.Rule
  Encapsulates a CSS Rule, of the form:
  
  selector{ propertyName1:propertyValue1; --- ; propertyNamen:propertyValuen; } @author Adam Tacy @version 3.0
• org.allspice.parser.Rule
  Represents a production. A production is of the form A->BCD. Every production has a reduction rule that translates the objects created from its rhs into a single object. @author egoff
• org.antlr.gunit.swingui.model.Rule
  ANTLR v3 Rule Information. @author scai
• org.antlr.tool.Rule
  Combine the info associated with a rule.
• org.antlr.v4.tool.Rule
• org.apache.commons.digester.Rule
  Concrete implementations of this class implement actions to be taken when a corresponding nested pattern of XML elements has been matched.

  Writing a custom Rule is considered perfectly normal when using Digester, and is encouraged whenever the default set of Rule classes don't meet your requirements; the digester framework can help process xml even when the built-in rules aren't quite what is needed. Creating a custom Rule is just as easy as subclassing javax.servlet.http.HttpServlet for webapps, or javax.swing.Action for GUI applications.

  If a rule wishes to manipulate a digester stack (the default object stack, a named stack, or the parameter stack) then it should only ever push objects in the rule's begin method and always pop exactly the same number of objects off the stack during the rule's end method. Of course peeking at the objects on the stacks can be done from anywhere.

  Rule objects should be stateless, ie they should not update any instance member during the parsing process. A rule instance that changes state will encounter problems if invoked in a "nested" manner; this can happen if the same instance is added to digester multiple times or if a wildcard pattern is used which can match both an element and a child of the same element. The digester object stack and named stacks should be used to store any state that a rule requires, making the rule class safe under all possible uses.

• org.apache.commons.digester3.Rule
  Concrete implementations of this class implement actions to be taken when a corresponding nested pattern of XML elements has been matched.

  Writing a custom Rule is considered perfectly normal when using Digester, and is encouraged whenever the default set of Rule classes don't meet your requirements; the digester framework can help process xml even when the built-in rules aren't quite what is needed. Creating a custom Rule is just as easy as subclassing javax.servlet.http.HttpServlet for webapps, or javax.swing.Action for GUI applications.

  If a rule wishes to manipulate a digester stack (the default object stack, a named stack, or the parameter stack) then it should only ever push objects in the rule's begin method and always pop exactly the same number of objects off the stack during the rule's end method. Of course peeking at the objects on the stacks can be done from anywhere.

  Rule objects should be stateless, ie they should not update any instance member during the parsing process. A rule instance that changes state will encounter problems if invoked in a "nested" manner; this can happen if the same instance is added to digester multiple times or if a wildcard pattern is used which can match both an element and a child of the same element. The digester object stack and named stacks should be used to store any state that a rule requires, making the rule class safe under all possible uses.

• org.apache.fulcrum.intake.xmlmodel.Rule
  A Class for holding data about a constraint on a property. @author John McNally @author Thomas Vandahl @version $Id: Rule.java 670328 2008-06-22 09:34:11Z tv $
• org.apache.hivemind.schema.Rule
  Rules associated with {@link org.apache.hivemind.schema.Schema} elements.As the {@link org.apache.hivemind.schema.SchemaProcessor}works through the {@link org.apache.hivemind.Element} hiearchy, it invokesmethods on the Rules. @author Howard M. Lewis Ship
• org.apache.jetspeed.rewriter.rules.Rule
  Rule @author David Sean Taylor @version $Id: Rule.java 516448 2007-03-09 16:25:47Z ate $
• org.apache.log4j.rule.Rule
  A Rule evaluates to true of false given a LoggingEvent object, and can notify listeners when the underlying implementation of this Rule has it's criteria changed by using the standard PropertyChangeListener infrastructure. @author Paul Smith @author Scott Deboy
• org.apache.marmotta.kiwi.reasoner.model.program.Rule
  This class is used to represent a reasoning rule of the form BODY -> HEAD where BODY is a list of graph patterns with variables and HEAD is a single graph pattern used for constructing new triples.

  Rules are always in disjunctive normal form, i.e. the BODY contains only conjunctions of patterns and no disjunctions, and the HEAD consists of only a single pattern.

  A graph pattern is of the form (S,P,O) or (S,P,O,C) where S is the subject, P the predicate, O the object, and C the context of a triple. S, P, and O may be either URIs, abbreviated local names or variables. C may only be a URI of abbreviated local name.

  Rules are "safe", i.e. variables occurring in the HEAD also have to appear at least once in the body. User: sschaffe

• org.apache.pig.experimental.plan.optimizer.Rule
  Rules describe a pattern of operators. They also reference a Transformer. If the pattern of operators is found one or more times in the provided plan, then the optimizer will use the associated Transformer to transform the plan.
• org.apache.pig.impl.plan.optimizer.Rule
  A rule for optimizing a plan. The rule contains a pattern that must be matched in the plan before the optimizer can consider applying the rule and a transformer to do further checks and possibly transform the plan. The rule pattern is expressed as a list of node names, a map of edges in the plan, and a list of boolean values indicating whether the node is required. For example, a rule pattern could be expressed as: [Filter, Filter] {[0, 1]} [true, true], which would indicate this rule matches two nodes of class name Filter, with an edge between the two, and both are required.
• org.apache.pig.newplan.optimizer.Rule
  Rules describe a pattern of operators. They also reference a Transformer. If the pattern of operators is found one or more times in the provided plan, then the optimizer will use the associated Transformer to transform the plan.
• org.apache.portals.applications.webcontent.rewriter.rules.Rule
  Rule @author David Sean Taylor @version $Id: Rule.java 764612 2009-04-13 21:17:59Z taylor $
• org.apache.provisionr.api.network.Rule
• org.apache.qpid.server.security.access.config.Rule
  An access control v2 rule. A rule consists of {@link Permission} for a particular identity to perform an {@link Action}. The identity may be either a user or a group.
• org.apache.stanbol.rules.base.api.Rule
  A Rule is a Java object that represent a rule in Stanbol. @author anuzzolese
• org.apache.tomcat.util.digester.Rule
  Concrete implementations of this class implement actions to be taken when a corresponding nested pattern of XML elements has been matched.
• org.apache.turbine.services.intake.xmlmodel.Rule
  A Class for holding data about a constraint on a property. @author John McNally @version $Id: Rule.java 278822 2005-09-05 19:53:05Z henning $
• org.apache.uima.annotator.regex.Rule
  Rule interface defines the access to the Rule settings and allows to add new Rule settings.
• org.apache.whirr.service.FirewallManager.Rule
• org.archive.accesscontrol.model.Rule
  An access control rules. Rules are organized into a tree based on SURT components. The leafmost (most specific) matching rule takes precedence. In the case that there are multiple matching rules for a particular node, allow takes precedence over deny which takes precedence over robots. @author aosborne
• org.beangle.ems.rule.Rule
• org.beangle.rule.Rule
• org.dom4j.rule.Rule

  Rule matches against DOM4J Node so that some action can be performed such as in the XSLT processing model.

  @author James Strachan @version $Revision: 1.7 $
• org.drools.core.rule.Rule
  A Rule contains a set of Tests and a Consequence.

  The Tests describe the circumstances that representrepresent a match for this rule. The Consequence gets fired when the Conditions match.

• org.drools.decisiontable.model.Rule
  @author Michael Neale Represents a rule.
• org.drools.definition.rule.Rule
  Public Rule interface for runtime rule inspection.
• org.drools.eclipse.core.Rule
  This represents a rule.
• org.drools.rule.Rule
  A Rule contains a set of Conditions and a Consequence.

  The Conditions describe the circumstances that representrepresent a match for this rule. The Consequence gets fired when the Conditions match. @see Condition @see Consequence @author bob mcwhirter @author Simon Harris @author mark pro

• org.drools.template.model.Rule
  Represents a rule.
• org.emftrace.metamodel.RuleModel.Rule
• org.geotools.styling.Rule
  l.opengeospatial.org/files/?artifact_id=1188"> OGC Styled-Layer Descriptor Report (OGC 02-070) version 1.0.0.:

   <xsd:element name="Rule"> <xsd:annotation> <xsd:documentation> A Rule is used to attach property/scale conditions to and group the individual symbolizers used for rendering. </xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:sequence> <xsd:element ref="sld:Name" minOccurs="0"/> <xsd:element ref="sld:Title" minOccurs="0"/> <xsd:element ref="sld:Abstract" minOccurs="0"/> <xsd:element ref="sld:LegendGraphic" minOccurs="0"/> <xsd:choice minOccurs="0"> <xsd:element ref="ogc:Filter"/> <xsd:element ref="sld:ElseFilter"/> </xsd:choice> <xsd:element ref="sld:MinScaleDenominator" minOccurs="0"/> <xsd:element ref="sld:MaxScaleDenominator" minOccurs="0"/> <xsd:element ref="sld:Symbolizer" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> 

  @source $URL$
• org.gradle.api.Rule

  A {@code Rule} represents some action to perform when an unknown domain object is referenced. The rule can use thedomain object name to add an implicit domain object.

• org.infinispan.protostream.descriptors.Rule
• org.intellij.sonar.sonarserver.Rule
• org.jacoco.report.check.Rule
  A rule applies for a certain element type and can define any number of limits for all elements of this type.
• org.jboss.byteman.rule.Rule
  A rule ties together an event, condition and action. It also maintains a TypeGroup identifying type information derived from these components.
• org.jboss.dna.connector.federation.Projection.Rule
• org.jboss.dna.graph.connector.federation.Projection.Rule
• org.jboss.seam.pages.Rule
• org.jboss.security.xacml.sunxacml.Rule
  Represents the RuleType XACML type. This has a target for matching, and encapsulates the condition and all sub-operations that make up the heart of most policies. @since 1.0 @author Seth Proctor
• org.jets3t.service.model.LifecycleConfig.Rule
• org.jivesoftware.openfire.plugin.rules.Rule
• org.kie.api.definition.rule.Rule
• org.kie.workbench.common.services.refactoring.model.index.Rule
• org.kuali.rice.kew.api.rule.Rule
• org.languagetool.rules.Rule
  Abstract rule class. A Rule describes a language error and can test whether a given pre-analyzed text contains that error using the {@link Rule#match(org.languagetool.AnalyzedSentence)}method. @author Daniel Naber
• org.midonet.client.resource.Rule
• org.objectstyle.wolips.ruleeditor.model.Rule
  @author uli @author Henrique Prange
• org.ocpsoft.rewrite.config.Rule
  Encapsulates correlated {@link Condition} and {@link Operation} instances. @author Lincoln Baxter, III
• org.opengis.style.Rule
  eospatial.org/standards/symbol">Symbology Encoding Implementation Specification 1.1.0 @author Open Geospatial Consortium @author Johann Sorel (Geomatys) @author Chris Dillard (SYS Technologies) @since GeoAPI 2.2
• org.openhab.model.rule.rules.Rule
• org.openxri.xri3.impl.parser.Rule
• org.openxri.xri3.impl.parser.Rule$xri
• org.parboiled.Rule
  Describes the return values of parser rule production methods.
• org.pdf4j.saxon.trans.Rule
  Rule: a template rule, or a strip-space rule used to support the implementation
• org.roolie.Rule

  All rules used by Roolie must implement this interface.

  In general, a Rule will be responsible for evaluating a "bite-sized" aspect of an application (i.e. Is a number in a given range? Is a user logged in?). These rules can be chained together with other rules to build more complex rules using the configuration file, although they may be used individually as well.

  Rule implementation class requirements:

  • Must have a no-arg constructor.
  • If the Roolie mechanism of populating properties from the configuration file is used, properties must be java.lang.String or java.util.List<String> (Of course you may parse them to whatever data type you wish when you use those values).
  • Wrap checked exceptions in unchecked exceptions within the passes() method, or handle them there.

• org.sbml.jsbml.Rule
  The base class for the {@link AlgebraicRule}, {@link RateRule}, {@link AssignmentRule}. @author Andreas Dräger @since 0.8 @version $Rev: 1531 $
• org.sonar.api.batch.rule.Rule
  @since 4.2
• org.sonar.api.rules.Rule
• org.sonar.check.Rule
• org.sonar.server.rule.Rule
  @since 4.4
• org.sonar.wsclient.rule.Rule
  @since 3.6
• org.sonar.wsclient.services.Rule
• org.w3c.www.protocol.http.proxy.Rule
  The authorization rule adds Basic credentials to all requests.
• org.wso2.carbon.rule.common.Rule
• our.apache.commons.digester.Rule
• rocket.style.client.Rule
  Each instance of this class represents a single Rule belonging to a StyleSheet @author Miroslav Pokorny (mP)
• ru.bmstu.datalog.data.Rule
  Realizes the representation Datalog rule. @author art-vybor
• rulesystem.Rule
  This class models a rule in the rule system. It has input columns and an output value which the rule system maps these inputs to. @author Kislay
• urban.kappa.Rule
  A representation of the model object 'Rule'.

  The following features are supported:

  • {@link urban.kappa.Rule#getName Name}
  • {@link urban.kappa.Rule#getLhs Lhs}
  • {@link urban.kappa.Rule#getRhs Rhs}

  @see urban.kappa.KappaPackage#getRule() @model @generated
• urban.model.Rule
  Line of the form "'name' A(x),A(y) <-> A(x!1),A(y!1) @ 1, 2"
• urban.urban.Rule
  A representation of the model object 'Rule'.

  The following features are supported:

  • {@link urban.urban.Rule#getName Name}
  • {@link urban.urban.Rule#getLhs Lhs}
  • {@link urban.urban.Rule#getRhs Rhs}

  @see urban.urban.UrbanPackage#getRule() @model @generated
• weka.associations.tertius.Rule
  Class representing a rule with a body and a head. @author Amelie Deltour @version $Revision: 1.7 $
• weka.classifiers.trees.m5.Rule
  Generates a single m5 tree or rule @author Mark Hall @version $Revision: 6260 $

Examples of urban.kappa.Rule

Examples of urban.model.Rule

Examples of urban.urban.Rule

Examples of weka.associations.tertius.Rule

Examples of weka.classifiers.trees.m5.Rule