Author: claimsbot

1-16. (canceled)
17. A fuel rail assembly for a fuel-injected spark-ignited internal combustion engine comprising:
first and second fuel rails, each said fuel rail formed by a tube having a plurality of injector outlets, at least one fuel rail having an inlet for receiving pressurized fuel, and each said fuel rail having an orifice to allow for fluid communication between said fuel rails;
a metal crossover tube for communicating fuel between said fuel rails, said tubes having a connection at opposite ends within each said rail; and
at least one fluid flow restrictor at one of said tube connections for damping pressure pulsations within said rails and to balance flow therebetween.
18. A fuel rail assembly for a fuel-injected spark-ignited internal combustion engine comprising:
first. and second fuel rails, each said fuel rail formed by a tube having a plurality of injector outlets, at least one fuel rail having an inlet for receiving pressurized fuel, and each said fuel rail having an orifice to allow for fluid communication between said fuel rails;
a crossover conduit for communicating fuel between said fuel rails, said crossover conduit having a connection at opposite ends within each said rail; and
at least one fluid flow restrictor at one of said crossover conduit connections for damping pressure pulsations within said rails and to balance flow therebetween.
19. A fuel rail assembly as described in claim 18 wherein said fuel rails are parallel spaced from one another.
20. A fuel rail assembly as described in claim 18 wherein each of said first and second fuel rails has at least two separate orifices to allow for fluid communication of fuel between said fuel rails and wherein there is a second crossover conduit for communicating fuel between the fuel rails, said second crossover conduit having opposite end connections with said fuel rail orifices.
21. A fuel rail assembly as described in claim 20 wherein said first and second crossover conduits are non-symmetric with one another.
22. A fuel assembly as described in claim 21 wherein at least one of said cross over conduits has a fluid flow restrictor.
23. A fuel assembly as described in claim 20 wherein said second crossover conduit has a polymeric main body with a flattened portion for damping pressure pulsations.
24. A fuel assembly as described in claim 18 wherein a connector fitting joins said fuel rail with said cross over conduit.
25. A fuel assembly as described in claim 24 wherein said connector fitting is connected with said fluid flow restrictor.
26. A fuel assembly as described in claim 24 wherein said connector fitting is a male barbed member and said crossover conduit is a polymeric hose.
27. A fuel assembly as described in claim 25 wherein said connector fitting is a male barbed member and said crossover conduit is a polymeric hose.
28. A fuel assembly as described in claim 18 wherein said crossover conduit has a fluid flow restrictor at both end connections with said fuel rails.
29. A fuel assembly as described in claim 28 wherein said crossover conduit fluid flow restrictors differ in fluid resistance.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1-78. (canceled)
79. A digital rights management (DRM) method in a terminal, comprising:
requesting information on a right to use a particular content from a card DRM agent;
receiving the information on the right from the card DRM agent, wherein the information includes a meta data for the right and state information for the right;
decoding the particular content using the information on the right; and
requesting an update of the state information from the card DRM agent, when a usage of the content is finished.
80. The method of claim 79, wherein the requesting of the update further comprises:
updating the state information according to the usage of the content; and
transmitting the updated state information to the card DRM agent.
81. The method of claim 79, further comprising:
receiving a response to the requesting of the update from the card DRM agent.
82. The method of claim 79, wherein the right corresponds to a stateful right.
83. A digital rights management (DRM) method in a card, comprising:
receiving a request for information on a right to use a particular content from a terminal;
transmitting the information on the right to the terminal, wherein the information includes a meta data for the right and state information for the right;
receiving a request of an update of the state information from the terminal, when the terminal finishes a usage of the content; and
updating the state information in response to the request of the update.
84. The method of claim 83, wherein the receiving of the request of the update further comprises:
receiving previously updated state information from the terminal.
85. The method of claim 83, wherein the updating further comprises:
replacing previously stored state information with updated state information.
86. The method of claim 83, further comprising:
transmitting a response to the request of the update to the terminal.

1. A computer-implemented method comprising:
receiving user input pertaining to a composition candidate associated with a plurality of service candidates in a service-oriented architecture (SOA) service model; and
updating the SOA service model based on the user input.
2. The method of claim 1, wherein:
the user input pertains to a new composition candidate; and
updating the SOA service model comprises adding the new composition candidate to the SOA service model.
3. The method of claim 2, further comprising:
in response to the user input, determining whether a number of service candidates in the SOA model is greater than one; and
disallowing an addition of the new composition candidate if the number of service candidates is not greater than one.
4. The method of claim 2, further comprising providing an add composition candidate user interface having an add composition candidate window to receive user input pertaining to the new composition candidate.
5. The method of claim 4, wherein the add composition candidate window comprises one or more composition candidate fields including one or more of a name field, an owner field, a composition members field, or a short description field.
6. The method of claim 5, wherein the add composition candidate window comprises an annotate control to initiate a word processor for receiving annotations for the composition candidate from the user.
7. The method of claim 4, wherein the add composition candidate user interface further comprises a profile window to display profile information for the composition candidate based on information entered in the add composition candidate window.
8. The method of claim 1, wherein:
the user input pertains to service candidates to be linked to the composition candidate; and
updating the SOA service model comprises associating the service candidates with the composition candidate in the SOA service model.
9. The method of claim 8, further comprising providing a model service composition candidate user interface comprising an inventory sidebar to display a plurality of service candidates in the SOA service model, and a main workspace to display a subset of the plurality of service candidates selected by the user from the sidebar for the composition candidate.
10. The method of claim 9, wherein the model service composition candidate user interface allows the user to drag the subset of the plurality of service candidates from the inventory sidebar to the main workspace for linking to the composition candidate.
11. The method of claim 9, further comprising:
incrementing a services counter for each service candidate linked to the composition candidate;
storing the services counter for the composition candidate in the SOA service model; and
displaying the services counter to the user in the main workspace.
12. The method of claim 9, further comprising:
receiving user input regarding operation relationships between the service candidates in the composition;
storing the operation relationships in the SOA service model;
updating an operation relationship counter for the composition candidate based on a number of operation relationships in the composition candidate;
storing the operation relationship counter for the composition candidate in the SOA service model; and
displaying the operation relationship counter to the user in the main workspace.
13. The method of claim 12, further comprising:
identifying a requestor and a provider of each of the operation relationships, the requester being an operation candidate associated with one of the service candidates in the composition candidate that is designated to initiate a data exchange, and the provider being an operation candidate associated with another one of the service candidates that is designated to respond to the requestor;
updating a requestor counter and a provider counter for each service candidate associated with the composition candidate based on a number of requester operation candidates and a number of provider operation candidates in a relevant service;
storing the requester counter and the provider counter for each service candidate of the composition candidate in the SOA service model; and
visually signifying the requestor operation candidate in the composition candidate in the main workspace.
14. The method of claim 8, further comprising:
receiving a user request to create a new service candidate to be linked to the composition candidate;
presenting an add service candidate user interface to the user;
receiving user input for the new service candidate via the add service candidate user interface;
adding the new service candidate to the SOA service model based on the user input; and
linking the new service candidate to the composition candidate in the SOA service model.
15. The method of claim 9, wherein the model service composition candidate user interface provides a visual indicator signifying that an operation candidate within one of the services in the composition encapsulates another composition, the visual indicator being selectable to open a modeling view of the other composition.
16. The method of claim 1, wherein:
the user input specifies modifications to an existing composition candidate; and
updating the SOA service model comprises updating the existing composition candidate in the SOA service model.
17. The method of claim 16, further comprising providing an edit composition candidate user interface comprising:
an edit composition candidate window with composition candidate fields;
a profile window to display profile information for the composition candidate being modified; and
an inventory side bar to display an inventory of composition candidates from the SOA service model and to highlight the composition candidate being modified.
18. The method of claim 1, wherein:
the user input identifies a composition candidate to be deleted; and
updating the SOA service model comprises deleting the composition candidate from the SOA service model.
19. The method of claim 18, further comprising providing a delete composition candidate user interface comprising:
an inventory side bar to display an inventory of composition candidates from the SOA service model and to highlight the composition candidate selected for deletion; and
a profile window to display profile information for the selected composition candidate.
20. A computer-implemented method comprising:
providing a first composition candidate view presenting service candidates associated with a first composition candidate, one of the services candidates including an operation candidate encapsulating a second composition candidate, the operation candidate being presented with an encapsulation indicator; and
upon a user selection of the operation candidate’s encapsulation indicator in the first composition candidate view, providing a second composition candidate view associated with the second composition candidate.
21. A computer-readable medium having executable instructions to cause a computer to perform a method comprising:
receiving user input pertaining to a composition candidate associated with a plurality of service candidates in a service-oriented architecture (SOA) service model; and
updating the SOA service model based on the user input.
22. The computer-readable medium of claim 21, wherein:
the user input pertains to a new composition candidate; and
updating the SOA service model comprises adding the new composition candidate to the SOA service model.
23. The computer-readable medium of claim 21, wherein:
the user input pertains to service candidates to be linked to the composition candidate; and
updating the SOA service model comprises associating the service candidates with the composition candidate in the SOA service model.
24. The computer-readable medium of claim 21, wherein:
the user input specifies modifications to an existing composition candidate; and
updating the SOA service model comprises updating the existing composition candidate in the SOA service model.
25. An apparatus comprising:
a database to store a service-oriented architecture (SOA) service model defining a plurality of service candidates; and
a composition manager to receive user input pertaining to a composition candidate associated with two or more of the plurality of service candidates, and to update the SOA service model based on the user input.
26. The apparatus of claim 25, wherein:
the user input pertains to a new composition candidate; and
the composition manager is to add the new composition candidate to the SOA service model.
27. The apparatus of claim 26, wherein the composition candidate manager is to provide an add composition candidate user interface comprising an add composition candidate window to receive user input pertaining to the new composition candidate, and a profile window to display profile information for the composition candidate based on information entered in the add composition candidate window.
28. The apparatus of claim 25, wherein:
the user input pertains to services to be linked to the composition candidate; and
the composition manager is to associate the service candidates with the composition candidate in the SOA service model.
29. The apparatus of claim 26, wherein the composition candidate manager is to provide a model service candidate composition user interface comprising an inventory sidebar to display a plurality of service candidates in the SOA service model, and a main workspace to display a subset of the plurality of service candidates linked to the composition candidate, and to display operation relationships between the service candidates,
wherein the model service candidate composition user interface allows the user to drag the subset of the plurality of service candidates from the inventory sidebar to the main workspace for linking to the composition candidate.
30. The apparatus of claim, wherein:
the user input specifies modifications to an existing composition candidate; and
the composition candidate manager is to update the existing composition candidate in the SOA service model.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A method for producing an agglomerated material used for producing metallic iron, wherein the agglomerated material is produced by agglomerating a material mixture containing an iron-oxide-containing material, a carbonaceous reducing agent, a binder, and moisture; drying the material mixture; and charging and heating the material mixture in a moving hearth-type reducing furnace to reduce the iron oxide contained in the material mixture with the carbonaceous reducing agent, wherein a carbohydrate is used as the binder and the material mixture is left to stand for from 0.5 to 4 hours prior to the agglomeration.
2. The method of claim 1, wherein the carbohydrate is a monosaccharide.
3. The method of claim 1, wherein the carbohydrate is a disaccharide.
4. The method of claim 1, wherein the carbohydrate is a polysaccharide.
5. The method of claim 1, wherein the carbohydrate is one or more selected from the group consisting of glucose, fructose, mannose, galactose, tagatose, xylose, arabinose, ribulose, xylulose, lyxose, ribose, deoxyribose, saccharose, maltose, cellobiose, gentiobiose, melibiose, lactose, turanose, sophorose, trehalose, isotrehalose, isosaccharose, cellulose, starch, glycogen, carronin, laminaran, dextran, inulin, levan, mannan, xylan, and gum Arabic.
6. The method of claim 1, wherein the carbohydrate is starch.
7. The method of claim 1, wherein the carbohydrate is wheat flour, potato flour, sweet potato flour, corn flour, or tapioca flour.
8. The method of claim 1, wherein the ratio of the binder to the material mixture is from 0.5 percent by mass to 1.5 percent by mass.
9. The method of claim 1, wherein the ratio of the binder to the material mixture is from 0.7 percent to 1.2 percent by mass.
10. The method of claim 1, wherein the carbonaceous reducing agent has a carbon content of at least 70 percent by mass.
11. The method of claim 1, wherein the carbonaceous reducing agent has a carbon content of at least 80 percent.
12. The method of claim 1, wherein material mixture has a moisture content of about 2 to 15 percent by mass.
13. A method for producing an agglomerated material used for producing metallic iron, the method comprising making a material mixture containing an iron-oxide-containing material, a carbonaceous reducing agent, a carbohydrate binder, and moisture;
leaving the material mixture to stand for from 0.5 to 4 hours;
after the material mixture has stood for from 0.5 to 4 hours, agglomerating the material mixture;
drying the material mixture; and
charging and heating the material mixture in a moving hearth-type reducing furnace to reduce the iron oxide contained in the material mixture with the carbonaceous reducing agent.
14. The method of claim 13, wherein the carbohydrate is a monosaccharide.
15. The method of claim 13, wherein the carbohydrate is a disaccharide.
16. The method of claim 13, wherein the carbohydrate is a polysaccharide.
17. The method of claim 13, wherein the carbohydrate is one or more selected from the group consisting of glucose, fructose, mannose, galactose, tagatose, xylose, arabinose, ribulose, xylulose, lyxose, ribose, deoxyribose, saccharose, maltose, cellobiose, gentiobiose, melibiose, lactose, turanose, sophorose, trehalose, isotrehalose, isosaccharose, cellulose, starch, glycogen, carronin, laminaran, dextran, inulin, levan, mannan, xylan, and gum Arabic.
18. The method of claim 13, wherein the carbohydrate is starch.
19. The method of claim 13, wherein the carbohydrate is wheat flour, potato flour, sweet potato flour, corn flour, or tapioca flour.
20. The method of claim 13, wherein the ratio of the binder to the material mixture is from 0.5 percent by mass to 1.5 percent by mass.
21. The method of claim 13, wherein the ratio of the binder to the material mixture is from 0.7 percent to 1.2 percent by mass.
22. The method of claim 13, wherein the carbonaceous reducing agent has a carbon content of at least 70 percent by mass.
23. The method of claim 13, wherein the carbonaceous reducing agent has a carbon content of at least 80 percent.
24. The method of claim 13, wherein material mixture has a moisture content of about 2 to 15 percent by mass.