`
`A rule file specifies one or more rules used to configure the pathbuilding system.
`
`Below is the DTD for a rule file:
`
`<!ELEMENT RULES (RULE)*>
`
`<!ELEMENT RULE (PREDICATE,ROUTE)>
`<!ELEMENT PREDICATE EMPTY>
`
`<!ATTLIST PREDICATE value CDATA #REQUIRED>
`<!ELEMENT ROUTE (STEP)+>
`
`<!ELEMENT STEP ((BEAD,EDGE,SEED?)|
`(BEAD,SEED?,EDGE)|
`
`(SEED?,BEAD,EDGE)|
`
`(SEED?,EDGE,BEAD)|
`
`(EDGE,SEED?,BEAD)|
`
`(EDGE,BEAD,SEED?)|
`(SEED)|
`
`(LOOPBACK))>
`<!ELEMENT BEAD EMPTY>
`
`<!ATTLIST BEAD name CDATA #REQUIRED>
`<!ELEMENT EDGE EMPTY>
`
`<!ATTLIST EDGE name CDATA #REQUIRED>
`<!ELEMENT SEED EMPTY>
`
`<!ATTLIST SEED value CDATA #REQUIRED>
`<!ELEMENT LOOPBACK EMPTY>
`
`<!ATTLIST LOOPBACK edge CDATA #REQUIRED>
`
`Below is a sample rule file containing a single rule with one of each type of step:
`
`<RULES>
`
`<RULE>
`
`<PREDICATE value="namespace:"/>
`<ROUTE>
`
`<STEP>
`
`<SEED value="namespace:seed=string:foo"/>
`<BEAD name="pmtestbead"/>
`<EDGE name="encode"/>
`</STEP>
`
`<STEP>
`
`<SEED value="namespace:seed=string:foo"/>
`</STEP>
`
`<STEP>
`
`<BEAD name="pmtestbead"/>
`<EDGE name="encode"/>
`</STEP>
`
`<STEP>
`
`<LOOPBACK edge="decode"/>
`</STEP>
`
`</ROUTE>
`
`</RULE>
`
`</RULES>
`
`Rules are the primary mechanism for configuring Strings. A rule is defined as a sequence of one or
`more steps to execute when a specific set of conditions are true. The set of conditions is know as the
`predicate. The steps are known as the route. A predicate is implemented as a registry object that
`implements the compare interface. The result of the comparison determines whether Strings will
`execute the route. A route is composed of steps. There are several types of steps described in more
`detail below.
`
`Page 1 of 3
`
`Implicit Exhibit 2022
`Sonos v. Implicit, IPR2018-0766, -0767
`
`
`
`Step Types
`
`There are four types of STEP element described below.
`Edge Steps
`
`Edge steps are the simplest type of step. Edge steps have the following format:
`
`<STEP>
`
`<BEAD name="mybead"/>
`
`<EDGE name="encode"/>
`
`</STEP>
`
`An edge step explicitly identifies an edge. This will cause the pathbuilding system to route the path to
`the specified edge. The bead name must match the name of a registered bead schema. The edge
`name must match an edge name within that schema which is also the name used to register the edge
`with SOS_Edge_Register.
`Seed Steps
`
`Seed steps have the following format:
`
`<STEP>
`
`<SEED value="namespace:seed=string:foo"/>
`
`</STEP>
`
`Seed steps specify a namespace object to stack on the path. The effect of this is to make all of the
`names objects in the seed namespace visible in the path, and to hide corresponding objects that were
`inserted into the path upstream. While in this SDK you will typically see the Stringsprovided
`namespace class used to define seed objects, any class that supports the namespace, stack, and
`copy interfaces can be used.
`
`SeedEdge Steps
`
`SeedEdge steps are just an edge step and a seed step combined into a single step. SeedEdge
`steps have the following format:
`
`<STEP>
`
`<SEED value="namespace:seed=string:foo"/>
`
`<BEAD name="pmtestbead"/>
`
`<EDGE name="encode"/>
`
`</STEP>
`
`The seed part of the step is applied to the path before the edge is inserted into the path.
`
`Loopback Steps
`
`Loopback steps are the most dynamic and powerful type of step. Loopback steps have the following
`format:
`
`Page 2 of 3
`
`Implicit Exhibit 2022
`Sonos v. Implicit, IPR2018-0766, -0767
`
`
`
`<STEP>
`
`<LOOPBACK edge="decode"/>
`
`</STEP>
`
`The LOOPBACK element specifies the name of the edge to use as a source of loopback information.
`The value of the edge attribute must be the name of one of the edges of the bead currently on top of
`the loopback stack, and that edge must have a loopback attribute specified in its schema.
`
`Page 3 of 3
`
`Implicit Exhibit 2022
`Sonos v. Implicit, IPR2018-0766, -0767
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
