1460753030-d4a0640c-c714-4738-9c82-6b99db472e16

1.-9. (canceled)
10. A perfumery composition, odorant, or fragrance comprising a compound of formula (I)
wherein each of R1, R2, R3, R4, R5, R6, R7, R8, R9, and R10 are independently selected from the group consisting of H, CH3, and C2H5,
X is \u2014CH2OH,
n is selected from the group consisting of 0 and 1, and
the dotted line represents a double bond or a single bond.
11. The perfumery composition, odorant, or fragrance of claim 10, wherein the compound is present in about 0.1 to about 10 weight percent of the perfumery composition.
12. The perfumery composition, odorant, or fragrance of claim 10, further comprising at least one ingredient selected from the group consisting of solvents, carriers, stabilizers, emulsifiers, moisturizers, dispersants, diluents, thickeners, thinners, other odorants, and adjuvants.
13. The perfumery composition, odorant, or fragrance of claim 12, wherein the compound is present in about 0.1 to about 10 weight percent of the perfumery composition.
14. A process for preparation of the perfumery composition, odorant, or fragrance according to claim 10, wherein the process comprises:
reacting a compound of formula (Ia)
with an alcohol of formula (Ib)
to receive a compound of formula (Ic)
and reacting the compound of formula (Ic) with an acetic anhydride to receive the compound of formula (I).
15. A perfumery composition, odorant, or fragrance comprising a compound of formula (I)
wherein each of R1, R2, R3, R4, R5, R6, R7, R8, R9, and R10 are independently selected from the group consisting of H, CH3, and C2H5,
X is \u2014CH2OCOCH3,
n is selected from the group consisting of 0 and 1, and
the dotted line represents a double bond or a single bond.
16. The perfumery composition, odorant, or fragrance of claim 15, wherein the compound is present in about 0.1 to about 10 weight percent of the perfumery composition.
17. The perfumery composition, odorant, or fragrance of claim 15, further comprising at least one ingredient selected from the group consisting of solvents, carriers, stabilizers, emulsifiers, moisturizers, dispersants, diluents, thickeners, thinners, other odorants, and adjuvants.
18. The perfumery composition, odorant, or fragrance of claim 17, wherein the compound is present in about 0.1 to about 10 weight percent of the perfumery composition.
19. A process for preparation of the perfumery composition, odorant, or fragrance according to claim 15, wherein the process comprises:
reacting a compound of formula (Ia)
with an alcohol of formula (Ib)
to receive a compound of formula (Ic)
and reacting the compound of formula (Ic) with an acetic anhydride to receive the compound of formula (I).

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 computerized method for enabling access to a plurality of service engines, wherein each service engine enables access to service resources, comprising:
providing a plurality of service class implementations for service engines from different vendors, wherein each service class implementation provides an implementation of methods and objects from a same abstract service class, wherein the service class implementations for the service engines include both a client side service class and server side service class, wherein the client side service class includes methods and objects used to access information on resources available at one service engine, wherein the server side service class includes methods and objects to access information on resources available at the service engine, and wherein the client side service class methods are invoked on a client system and the server side service class methods are invoked on a server including the service engine;
receiving, at the client system, a construct method to construct a client side service object to access the service engine;
constructing the client side service object in response to the construct method;
communicating the construct method to the server to cause the server to construct a server side service object;
instantiating the server side service object for the service engine in response to the construct method, wherein the service object includes information on the service engine; and
issuing method calls from client applications in the client system to access information from the service engine using the constructed client-side and server side service objects.
2. The method of claim 1, wherein the method call is received from at least one application program including methods from at least one of the service class implementations to access information on at least one service from the service objects.
3. The method of claim 1, wherein the service engines comprise workflow products from different vendors, wherein the workflow products comprise computer programs enabling implementation of a computer implemented workflow defining a series of processes to be performed by users at computers with respect to a computer implemented work item.
4. The method of claim 3, wherein the workflow service class implementations from different vendors each includes methods and objects from a same abstract workilow service class specifying methods and objects to include in all workflow service class implementations.
5. The method of claim 4, wherein the abstract workflow service class specifies a method to determine a data store used by resources in the service, wherein the workflow service class implementations for the workflow services implement a method to determine from the service object for the service the data store used by the service.
6. The method of claim 4, wherein the abstract workflow service class specifies methods to access information on workilows, workflow templates, and worklists.
7. The method of claim 4, wherein the abstract workflow class specifies a method for a user to connect to the workilow service by passing user information that is used to authenticate the user to access the workflow service, and wherein the workilow service class implementations include methods to enable a connection between a user and one workflow service.
8. The method of claim 7, farther comprising:
receiving a method call for the user to connect specifying a user name, authentication information, and one service;
instantiating a connection object if authentication passed including information on the specified user name, authentication information, and the service engine that can be accessed with the authentication; and
returning a handle to the connection object for use in obtaining authentication information to access the service engine specified in the connection object.
9. The method of claim 8, wherein the connection object is stored in one service object.
10. The method of claim 1, further comprising:
receiving one handle to one connection object; and
returning authentication information from the connection object for use in accessing the service resources.
11. The method of claim 1, wherein a call to one method in the client side service class implementation on the client transfers the called method to the server, wherein the called method is executed on the server.
12. The method of claim 1, wherein information on the service engine is maintained in the service object and wherein using the service object to access the requested information further comprises:
if the method call requests information in the service object, returning the requested information from the service object.
13. The method of claim 12, further comprising:
if the method call requests information not included in the service object, executing the method to access the requested information from the service engine.
14. The method of claim 12, further comprising:
accessing authentication information from the service object;
providing the accessed authentication information to the service engine;
using, with the service engine, the accessed authentication information to authenticate access, wherein the service engine executes the method to access the requested information if access is authenticated.
15. The method of claim 13, wherein accessing the requested information from the service engine further comprises:
translating the method to native code capable of being executed by the service engine.
16. A system for enabling access to a plurality of service engines, wherein each service engine enables access to service resources, comprising:
(a) a client system, including:
(i) a client computer readable medium, wherein the client computer readable medium stores a client side service class, and wherein the client side service class includes methods and objects used to access information on resources available at one service engine;
(ii) means for receiving a construct method to construct a client side service object to access the service engine;
(iii) means for constructing the client side service object in response to the construct method;
(iv) means for communicating the construct method to the server to cause the server to construct a server side service object; and
(v) means for issuing method calls from client applications in the client system to access information from the service engine using the constructed client-side and server side service objects; and

(b) a server system, including:
(i) a server computer readable medium, wherein the server computer readable medium stores server side service class implementations for service engines from different vendors, and wherein the server side service class includes methods and objects to access information on resources available at the service engines from a same abstract service class; and

(ii) means for instantiating a service object in the server computer readable medium for the service engine in response to the construct method wherein the service object includes information on the service engine.
17. The system of claim 16, wherein the method call is received from at least one application program including methods from at least one of the service class implementations to access information on at least one service from the service objects.
18. The system of claim 16, wherein the service engines comprise workflow products from different vendors, and wherein the at least one computer readable medium includes workflow service class implementations from different vendors, wherein the workflow products comprise computer programs enabling implementation of a computer implemented workflow defining a series of processes to be performed by users at computers with respect to a computer implemented work item.
19. The system of claim 18 wherein the workilow service class implementations from different vendors each includes methods and objects from a same abstract workilow service class specifying methods and objects to include in all workilow service class implementations.
20. The system of claim 19, wherein the abstract workflow service class specifies a method to determine a data store used by resources in the service, wherein the workflow service class implementations for the workflow services implement a method to determine from the service object for the service the data store used by the service.
21. The system of claim 19, wherein the abstract workflow service class specifies methods to access information on workilows, workflow templates, and worklists.
22. The system of claim 19, wherein the abstract workflow class specifies a method for a user to connect to the workilow service by passing user information that is used to authenticate the user to access the workflow service, and wherein the workilow service class implementations include methods to enable a connection between a user and one workflow service.
23. The system of claim 22, further comprising:
means for receiving a method call for the user to connect specifying a user name, authentication information, and one service;
means for instantiating a connection object in one computer readable medium if authentication passed, wherein the connection object includes information on the specified user name, authentication information, and the service engine that can be accessed with the authentication; and
means for returning a handle to the connection object for use in obtaining authentication information to access the service engine specified in the connection object.
24. The system of claim 23, wherein the connection object is stored in one service object in the computer readable medium.
25. The system of claim 16, further comprising:
means for receiving one handle to one connection object; and
means for returning authentication information from the connection object for use in accessing the service resources.
26. The system of claim 16, further comprising:
means for transferring a call to one method in the client side service class implementation on the client to the server, wherein the called method is executed on the server.
27. The system of claim 16, wherein information on the service engine is maintained in the service object and wherein using the service object to access the requested information further comprises:
means for returning the requested information from the service object if the method call requests information in the service object.
28. The system of claim 27, further comprising:
means for executing the method to access the requested information from the service engine if the method call requests information not included in the service object.
29. The system of claim 27, further comprising:
means for accessing authentication information from the service object; and
means for providing the accessed authentication information to the service engine, wherein the service engine uses the accessed authentication information to authenticate access, wherein the service engine executes the method to access the requested information if access is authenticated.
30. The system of claim 27, wherein the means for executing the method to access the requested information from the service engine further performs:
translating the method to native code capable of being executed by the service engine.
31. An article of manufacture comprising a computer readable medium storing code executed by a computer for enabling access to a plurality of service engines, wherein each service engine enables access to service resources, wherein the code is capable of causing operations to be performed, the operations comprising:
providing a plurality of service class implementations for service engines from different vendors, wherein each service class implementation provides an implementation of methods and objects from a same abstract service class, wherein the service class implementations for the service engines include both a client side service class and server side service class, wherein the client side service class includes methods and objects used to access information on resources available at the service engine, wherein the server side service class includes methods and objects to access information on resources available at one service engine, and wherein the client side service class methods are invoked on a client system and the server side service class methods are invoked on a server including the service engine;
receiving, at the client system, a construct method to construct a client side service object to access the service engine;
constructing the client side service object in response to the construct method;
communicating the construct method to the server to cause the server to construct a server side service object;
instantiating the server side service object for one service engine in response to the construct, wherein the service object includes information on the service engine; and
issuing method calls from client applications in the client system to access information from the service engine using the constructed client-side and server side service objects.
32. The article of manufacture of claim 31, wherein the method call is received from at least one application program including methods from at least one of the service class implementations to access information on at least one service from the service objects.
33. The article of manufacture of claim 31, wherein the service engines comprise workilow products from different vendors, wherein the workflow products comprise computer programs enabling implementation of a computer implemented workilow defining a series of processes to be performed by users at computers with respect to a computer implemented work item.
34. The article of manufacture of claim 33, wherein the workilow service class implementations from different vendors each includes methods and objects from a same abstract workilow service class specifying methods and objects to include in all workflow service class implementations.
35. The article of manufacture of claim 34, wherein the abstract workflow service class specifies a method to determine a data store used by resources in the service, wherein the workilow service class implementations for the workilow services implement a method to determine from the service object for the service the data store used by the service.
36. The article of manufacture of claim 34, wherein the abstract workflow service class specifies methods to access information on workflows, workflow templates, and worklists.
37. The article of manufacture of claim 34, wherein the abstract workflow class specifies a method for a user to connect to the workilow service by passing user information that is used to authenticate the user to access the workilow service, and wherein the workilow service class implementations include methods to enable a connection between a user and one workflow service.
38. The article of manufacture of claim 37, further comprising:
receiving a method call for the user to connect specifying a user name, authentication information, and one service;
instantiating a connection object if authentication passed including information on the specified user name, authentication information, and the service engine that can be accessed with the authentication; and
returning a handle to the connection object for use in obtaining authentication information to access the service engine specified in the connection object.
39. The article of manufacture of claim 38, wherein the connection object is stored in one service object.
40. The article of manufacture of claim 31, further comprising:
receiving one handle to one connection object; and
returning authentication information from the connection object for use in accessing the service resources.
41. The article of manufacture of claim 31, wherein a call to one method in the client side service class implementation on the client transfers the called method to the server, wherein the called method is executed on the server.
42. The article of manufacture of claim 31, wherein information on the service engine is maintained in the service object and wherein using the service object to access the requested information further comprises:
if the method call requests information in the service object, returning the requested information from the service object.
43. The article of manufacture of claim 42, further comprising:
if the method call requests information not included in the service object, executing the method to access the requested information from the service engine.
44. The article of manufacture of claim 42, further comprising:
accessing authentication information from the service object;
providing the accessed authentication information to the service engine; and
using, with the service engine, the accessed authentication information to authenticate access, wherein the service engine executes the method to access the requested information if access is authenticated.
45. The article of manufacture of claim 43, wherein accessing the requested information from the service engine further comprises:
translating the method to native code capable of being executed by the service engine.

1460753022-fc0aa739-389d-42d6-a45d-4b34fea5f12c

1. A system for managing product inventory comprising: an Internet-connected server; a media repository containing videos; and software executing on the server from a non-transitory physical medium, the software providing:
establishment using the server of a first association in memory of the server of at least one stock keeping unit (SKU) of a product and associated metadata including product availability counts to a video identifier and at least one point in time within an interactive shopping video presentation of one of the videos from the media repository;
establishment using the server of a second association of at least one potential consumer to the interactive shopping video presentation;
using the server, causing displaying within a single interactive shopping interface, in communication with any of a laptop, smart phone or desktop computer of the potential consumer, the interactive shopping video presentation and two or more interactive components embedded in one of the videos of the interactive shopping video presentation, the interactive components comprising two or more of: video overlays, interactive pop-up screens, interactive purchase icons, or buttons; and wherein one of the interactive components is configured to be manipulated to initiate an interaction sequence resulting in a purchase;
using the server, monitoring for and tracking of interaction sequences initiated by the at least one potential consumer, using any of the laptop, smart phone or desktop computer, the interaction sequences enabled from within the interactive shopping video presentation using an interactive component, the monitoring including detecting selection of a particular button;
automatic adjustment, in real-time, using the server of the product availability counts associated with the interactive shopping video presentation based upon the interaction sequences that have been monitored for and tracked;
at the at least one point in time or later during playing the interactive shopping video presentation, and coinciding with a displayed representation of a particular product, determining using the server based upon the current product availability counts that a particular product is not available for purchase, and in response, automatically using the server, causing disabling the displaying on any of the laptop, smart phone or desktop computer a particular interactive component that would initiate a transaction to purchase the particular product.
2. The system of claim 1, wherein the associated metadata includes one or a combination of color, size, quantity, price, and credits available, if any, along with the current product inventory count.
3. The system of claim 1, wherein the point in time coincides with a graphic or audio representation of the particular product.
4. The system of claim 1, wherein a second one of the interactive components is visible at the at least one point in time.
5. The system of claim 1, wherein the establishment of the second association is dynamic and automatic.
6. The system of claim 4, wherein the second one of the interactive components is one of a visual overlay, a text box, a link to an order form, or a purchasing icon.
7. The system of claim 1, wherein the software further provides a posting interface, the posting interface adapted to enable posting of comments and recommendations by potential consumers associated with the interactive shopping video presentation.
8. The system of claim 7, wherein the posting interface creates a third dynamic association of at least one tip, recommendation, or comment to at least one point in time and or at least one time range within the interactive shopping video presentation.
9. The system of claim 1, wherein the interaction sequences initiated within the interactive shopping video presentation by the at least one potential consumer continue on a transaction server.
10. The system of claim 1, wherein the product availability counts are adjusted dynamically during accounting based on number of confirmed purchases.
11. The system of claim 1, wherein product inventory is dynamically reordered or replenished to updated counts based on count thresholds triggered through count adjustments relative to consumer interaction results.
12. A method for managing product inventory comprising:
(a) using an Internet-connected server, creating and storing a mapping in memory of the server that associates product stock keeping units (SKUs) of products, associated metadata, and current product availability counts to a video identifier and at least one point in time an interactive shopping video presentation of one of videos stored in a media repository containing videos;
(b) using the server, mapping at least one potential consumer to the interactive shopping video presentation;
(c) using the server, causing displaying within a single interactive shopping interface, in communication with any of a laptop, smart phone or desktop computer of the potential consumer, the interactive shopping video presentation and two or more interactive components embedded in one of the videos of the interactive shopping video presentation, the interactive components comprising two or more of: video overlays, interactive pop-up screens, interactive purchase icons, or buttons; and wherein one of the interactive components is configured to be manipulated to initiate an interaction sequence resulting in a purchase;
(d) using the server, monitoring and tracking interaction sequences initiated by the at least one potential consumer, using any of the laptop, smart phone or desktop computer, the interaction sequences enabled from within the interactive shopping video presentation using an interactive component, the monitoring including detecting selection of a particular button;
(e) in real-time, using the server, automatically adjusting the current product availability counts associated with the interactive shopping video presentation based upon the interaction sequences that are monitored and tracked in step (d);
using the server, at the at least one point in time or later during playing the interactive shopping video presentation and coinciding with a displayed representation of a particular product, determining based upon the current product availability counts that a particular product is not available for purchase, and in response, automatically using the server, causing disabling the displaying on any of the laptop, smart phone or desktop computer, an interactive component that would initiate a transaction to purchase the particular product.
13. The method of claim 12, wherein the associated metadata includes one or a combination of color, size, quantity, price, and credits available, if any, along with the current product inventory counts.
14. The method of claim 12, wherein in step (a), the point in time coincides with a graphic or audio representation of the particular product.
15. The method of claim 12, wherein a second one of the interactive components is visible at the at least one point in time.
16. The method of claim 15, wherein the second one of the interactive components is one of a visual overlay, a text box, a link to an order form, or a purchasing icon.
17. The method of claim 12 comprising updating an inventory count of a product repository that is associated with the metadata based upon the interaction sequences that are monitored and tracked.
18. The method of claim 12 wherein the interactive component comprises an interactive order form.
19. The method of claim 12 further comprising, as new product is stocked, updating the product availability counts of the metadata associated with a plurality of video presentations.
20. The method of claim 12 further comprising:
at the at least one point in time or later during playing the interactive shopping video presentation, determining that a particular current product availability count for a particular product is negative;
in response, enabling the interactive component that would initiate a transaction to purchase the particular product.
21. The method of claim 12 further comprising:
facilitating a single transaction comprising a confirmed purchase of one or more products;
in response to the single transaction, causing an update to a plurality of the current product availability counts for a plurality of video presentations all of which include the one or more products.
22. A data processing method comprising:
using an Internet-connected server, creating and storing a mapping in memory of the server that associates video identifiers of interactive shopping video presentations, any of cue points, time stamps, time windows or time ranges within the video presentations, and product stock keeping units (SKUs) of products that are displayed within the video presentations of one of videos stored in a media repository containing videos;
using the server, causing displaying within a single interactive shopping interface, in communication with any of a laptop, smart phone or desktop computer of the potential consumer, the interactive shopping video presentation and two or more interactive components embedded in one of the videos of the interactive shopping video presentation, the interactive components comprising two or more of: video overlays, interactive pop-up screens, interactive purchase icons, or buttons; and wherein one of the interactive components is configured to be manipulated to initiate an interaction sequence resulting in a purchase;
using the server, providing, within each of the video presentations, associated metadata that is associated with each of the product SKUs, wherein the metadata includes current product availability counts for the products represented by the product SKUs;
using the server, monitoring interaction sequences of at least one potential consumer using any of the laptop, smart phone or desktop computer, the interaction sequences enabled from within the interactive shopping video presentation using an interactive component, the monitoring including detecting selection of a particular button;
in real-time, using the server, as the interaction sequences occur in the interactive shopping video presentation, automatically updating the current product availability counts associated with the particular interactive shopping video presentation based upon the interaction sequences;
using the server, at a particular time point during the playing and coinciding with a displayed representation of a particular product, determining based upon the mapping and the current product availability counts that a particular product is not available for purchase, and in response, automatically using the server, causing disabling the displaying on any of the laptop, smart phone or desktop computer, an interactive component that would initiate a transaction to purchase the particular product.

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 retractable bicycle fender comprising:
a) a spring strip; and
b) an elastomeric grommet

wherein:
c) said spring strip has a stable elongated configuration that forms said fender and a stable coiled configuration;
d) said spring strip forms a seat post hole without a break, said seat post hole having a diameter larger than the diameter of a bicycle seat post;
e) said elastomeric grommet is attached to said spring strip and surrounds said seat post hole forming a grommet hole with a wall; and
f) the diameter of said grommet hole is less than the diameter of said bicycle seat post such that said grommet will grip said bicycle seat post when said bicycle seat post is inserted through said grommet hole.
2. The bicycle fender of claim 1 which further comprises plastic wings wherein said plastic wings extend along each long edge of said spring strip.
3. The bicycle fender of claim 2 wherein said plastic wings increase the width of said bicycle fender to more than the width of said spring strip.
4. The bicycle fender of claim 1 wherein said wall of said grommet hole is at an angle with respect to the plane of said spring strip, said angle being in the range of 20 to 40 degrees.
5. The bicycle fender of claim 4 wherein said angle is about 30 degrees.
6. The bicycle fender of claim 1 wherein twin peaks of said elastomeric grommet are extended along the edges of said spring strip.
7. The bicycle fender of claim 1 wherein the diameter of said grommet hole is in the range of 20 mm to 26 mm.