Monteil, C. Quentin-Noury, M. Reverdy, M. Vergnaud, R. The in vitro activity of fusidic acid was evaluated against strains of streptococci isolated from skin and soft tissue infections during a prospective multicentre study. Groups A, B, C and G streptococci represented, respectively, The activity of fusidic acid was dependent on the media used. In both media, fusidic acid was moderately active against streptococci.
However, antibiotic concentrations obtained in the skin exceed the MIC 90 of fusidic acid for streptococci, possibly explaining its clinical efficacy in the treatment of common cutaneous infections. Oral fusidic acid has been shown to be effective for the treatment of patients with skin and soft tissues infections. However, in contrast to staphylococci, the in vitro activity of fusidic acid against streptococci has seldom been studied. To the best of our knowledge, no recent data are available.
We have studied the in vitro activity of fusidic acid against streptococci recently isolated from skin and soft tissue infections by the laboratories of 10 French hospitals. Only strains isolated from out-patients or in-patients hospitalized in medical and dermatological units were included in the study. Strains from surgical, intensive care or burns units were excluded.
A total of streptococcal strains were collected; Of these, The vast majority of isolates included groups A Group F and oral streptococci represented only 2. Fourteen isolates were from cases of erysipelas, due to six group A streptococci, seven group G streptococci and one group B streptococcus, and five isolates were from cases of necrotizing fasciitis, four due to group A and one to group G streptococci. A total of strains were studied for susceptibility to antibiotics. All were susceptible to ampicillin, cephalothin, penicillin G, pristinamycin and vancomycin; Thus, with regard to MICs, A similar trend was observed with the disc diffusion method Table II.
However, this latter method led to an overestimation of the intermediate and resistant strains in both agar media as compared with MICs Table II. The strains studied were collected mostly from outpatients and from dermatology and emergency units and therefore were probably responsible for community-acquired infections. As expected, groups A and G streptococci were predominant.
The in vitro activity of fusidic acid appeared different according to the medium used. The difference could be related to the presence or absence of blood in the medium. Whatever the technique used, fusidic acid appears to be moderately active against streptococci, although acquired resistance was rare. Possibly, the use of media supplemented with blood correlated better with the in vivo conditions.
Our results are in accord-ance with the few reports already published. For example resourceType is used by the Documents service to identify whether an object is a wiki, blog, or document. Determines whether links in the task flow launch content in inline popups false or in browser windows true. This section describes advanced features available with the Activity Graph service. The Activity Graph service provides a data control that enables you to create your own user interface task flows for the service.
The Activity Graph data control exposes two methods to query Activity Graph for suggestions of similar items and similar users, and one method to record items the user is not interested in.
Typically, there are three things that you need to bind your data control to a method: a MethodAction , a MethodIterator to iterate through the results of the method, and a Tree to pick attributes of the resulting data structure.
You can create these manually in a page definition file, or more easily, use the wizards that JDeveloper provides. Add the RecommendationDataControl to your project either by selecting it in the catalog, right-clicking and choosing Add to Project or by dragging and dropping it onto a JSP page.
This will automatically create a method action binding and an iterator to the resultant collection. Select the nodes that you want to expose. This will automatically create a Tree to access values in the suggestion.
Configure the parameters for the method action, typically these will be expressions that you would have defined as pageFlowScope variables. For example:. To find the entry point for the Activity Graph service, find the link element with a resourceType of:.
The corresponding href or template element provides the URI entry point. For more information about the Resource Index, see Section For more information about resource types, see Section When the client has identified the entry point, it can then navigate through the resource type taxonomy to perform the required operations.
For more information about the individual resource types, see the appropriate section in Section There are no specific security considerations for this service. For general security considerations, see Section This section provides you with all the information you need to know about each resource type.
The response from a GET operation includes each object in this collection of objects, and each object includes links used to operate on that object. The nodes provided out of the box are all WebCenter resources users, documents, Spaces, and so on and so have WebCenter service and resource IDs. If a service's objects are further classified by resource type, you must also specify that resource type. Any new node classes that are created that is, non-native WebCenter objects should be identified using node class and object URNs.
For information about these common parameters, see "Common Request Query Parameters". For example WC. For example monty , For example, gs-edit;gs-all The default value is WC. If you are integrating the Activity Graph engine with another application, this may need to be a different node class. Table lists the resource types that the client can link to from this resource. The recommendation response contains the recommended objects and the URIs for use in accessing those objects.
This section shows how the client can navigate through the hypermedia to access the recommendation resource:. Table lists the read-only elements for the recommendations resource. The overall score of the recommendation. This is the weighted sum of the component scores associated with each of the similarity URNs that comprise the recipe and is a floating point number between 0 and 1.
A list of the component scores associated with the different similarity URNs in the recipe for the recommendation. A component score may have a reason and a link which can be used to retrieve the common items that the user and the recommended object have interacted with.
Use this resource to identify the URI to use to retrieve GET objects with which the source object and recommended object have interacted. You can use this to determine the reasons why a particular object was recommended. The response from a GET operation includes each item in this collection of items, and each item includes links used to operate on that item.
For example item-tag , gs-edit , user-connect. Use this resource type to identify the URI to use to update PUT a recommendation to indicate user interest in the recommended object. This section shows how the client can navigate through the hypermedia to access the item resource:. User information about the user who last updated the object, including GUID, ID, display name, and a link to the profile icon. User information about the user who created the object, including GUID, ID, display name, and a link to the profile icon.
Out of the box, Activity Graph includes metadata definitions for mapping WebCenter service event data from Analytics. This metadata is automatically loaded the first time the Activity Graph engines application starts. The XML files can be exported, edited in a text editor, and then imported.
After exporting the metadata definitions to an appropriate file, you can then edit the file in an editor of your choice to add your own definitions. When you have made your changes, you must import the metadata file back to the managed server. The Activity Graph metadata provide definitions for the node classes that represent WebCenter objects, such as users, Spaces, and documents. For more information and for a list of the default node classes supported by WebCenter, see "Node Classes".
You can define your own node classes, for other WebCenter objects or for objects from other applications, by exporting the Activity Graph metadata definitions to an XML file, editing the file, and then importing the metadata back into WebCenter. For example, if you want to integrate your CRM application with Activity Graph, you could define a node class for service requests. URN —An attribute of the nodeClass element, this is a string that uniquely identifies the node class.
Valid values are Item or User. This enables you to integrate Activity Graph more efficiently with applications that use numeric IDs. Valid values are true or false. A node class's properties are available at runtime to provide additional metadata about the class. For example, all out-of-the-box WebCenter objects modeled in Activity Graph define properties for serviceID and resourceType , which are used by the Activity Graph task flows to tailor the display of recommendations based on their service and resource type:.
Activity Graph includes metadata definitions for the actions that occur in WebCenter Portal applications. For more information, see "Actions". You can define your own actions, for WebCenter or for other applications, by exporting the Activity Graph metadata definitions to an XML file, editing the file, and then importing the metadata back into WebCenter.
For example, if you want to integrate your CRM application with Activity Graph, you could define new actions for opening a service request, assigning a service request to a customer service representative, and closing a service request.
URN —An attribute of the action element, this is a string that uniquely identifies the action. Simple —These actions are useful for counting. They have no other metadata besides the source, the target, and the occurred time. For example, WebCenter comes with a preregistered view-count simple action whose associated relation value increases each time the person clicks on the same item, but also decays over time.
Boolean —These actions are useful when you just want to know whether something has happened or not, but not how many times it has happened. Boolean actions have one additional Boolean as metadata. For example, WebCenter comes with a Boolean view action whose associated relation value doesn't increase each time the person clicks on the same item. It just records whether a person has clicked on a specific item or not.
Non-negative Integer —Actions that have one additional integer as metadata, where the integer cannot be negative. Rating assigning a number of stars is the typical example. Integer —Actions that have one additional integer as metadata. This can be used for ratings that allow negative values.
An example of a symmetric action is the connect action, which occurs when two users connect in the People Connections service. Valid values are User or Item. Valid values are Sum or LastAssigned. Sum actions increment each time they occur, for example the edit-count action.
LastAssigned actions keep whatever value was passed in the most recent occurrence of the action. Non-counting simple actions like create and edit are LastAssigned.
An example of a LastAssigned Integer action would be a rating action. When computing the relation value, the value of each action is multiplied by the decay factor every decay period following the occurrence of the action. Activity Graph includes metadata definitions for the similarity calculations that are used by WebCenter. For more information, see "Similarity Calculations". You can define your own similarity calculations, for WebCenter or for other applications, by exporting the Activity Graph metadata definitions to an XML file, editing the file, and then importing the metadata back into WebCenter.
For example, if you want to integrate your CRM application with Activity Graph, you could define an item-assign similarity calculations for to help recommend other service requests that were assigned to the same person.
Edit the XML file to define the new similarity calculation. For each similarity calculation, you must specify:. URN —An attribute of the similarityCalculation element that is a string that uniquely identifies the similarity calculation. There is currently only one supported similarity function: Tanimoto.
This function measures similarity between two items as the ratio of the number of common actions to the total number of actions on those items. These are the targets of the actions represented in the similarity calculation's relation combination. Boolean OR is used by all WebCenter out-of-the-box similarity calculations and it simply states that the resulting relation combination has a value of 1 if an only if any of the constituent relations have a positive value.
A Weighted Sum relation combination is a linear combination of relation values, where the coefficients have to be specified as part of the combination. In the out-of-the-box metadata definitions, Weighted Sum relation combinations are used in rank calculations. Activity Graph includes metadata definitions for the rank calculations that are used by the Activity Graph Rank Engine to calculate the importance of nodes in the activity graph. You can define your own rank calculations, for WebCenter or for other applications, by exporting the Activity Graph metadata definitions to an XML file, editing the file, and then importing the metadata back into WebCenter.
Edit the XML file to define the new rank calculation. For each rank calculation, you must specify:. URN —An attribute of the rankCalculation element, this is a string that uniquely identifies the rank calculation. This class receives a set of object rankings from the Rank Engine and stores them in a search engine where they can later be used to influence search query ranking.
WebCenter includes one rank acceptor out of the box, which will persist ranks to Oracle Secure Enterprise Search. Activity providers are used by the Activity Graph engine during the gathering process to generate activities from recorded occurrences of actions.
For example, the Analytics Activity Provider reads actions from the Analytics event tables and uses a registered set of mappings to generate activities. These activities are then used to determine relations, which are used in turn to determine recommendations and search ranks. If you want to integrate other applications with the Activity Graph engine, you can create your own activity providers to generate activities from those applications.
To make a custom activity provider available to the Activity Graph engine, you must register it by adding an activity provider assignment to the Activity Graph metadata definitions.
An activity provider assignment maps the triple of the action , srcClass , and trgClass to the Java class that implements the activity provider. Edit the XML file to define the new activity provider assignment. For each activity provider assignment, you must specify:. Figures References Related Information. Cited By Maximizing the expected net present value in a project with uncertain cash flows. Designing practical coordinating contracts in decentralized projects.
A classification and review of approaches and methods for modeling uncertainty in projects. The preemptive stochastic resource-constrained project scheduling problem. Robust resource-constrained max-NPV project scheduling with stochastic activity duration. New strategies for stochastic resource-constrained project scheduling. Maximizing the expected net present value of a project with phase-type distributed activity durations: An efficient globally optimal solution procedure.
Metaheuristics for multi-mode cash flow balanced project scheduling with stochastic duration of activities. Incentive Contracts in Serial Stochastic Projects. Minimizing the expected makespan of a project with stochastic activity durations under resource constraints.
Project planning with alternative technologies in uncertain environments. Literature Review. Optimal project planning under the threat of a disruptive event. Setting gates for activities in the stochastic project scheduling problem through the cross entropy methodology. Predetermined intervals for start times of activities in the stochastic project scheduling problem. Project scheduling with alternative technologies: Incorporating varying activity duration variability.
0コメント