Loading patent…
AssigneeOracle International Corporation
InventorsJuan Ignacio Vimberg, Rodolfo José Cruz, Esteban Alejandro Capillo Carril
Estimating the term…
Implementations include a resource compatibility engine and method configured to verify resource compatibility when importing schemas and formats such as XSD and WSDL into a database table such as a business catalog. The resource compatibility engine may be configured to prevent possible catalog corruption from importing file types that do not match. The resource compatibility engine may also be employed to identify which are the resource file types that need to be overwritten in case of an update and provides useful feedback in case the import is not successful.
A non-transitory computer readable medium including one or more instructions executable by one or more processors for:
A computer implemented method comprising:
An apparatus for verifying compatibility between files in a computing environment, the computing environment comprising one or more computing devices in communication with a software application that executes software configured to provide information accessible to the one or more computing devices, a computing device of the one or more computing devices configured to:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
No references of this kind are recorded.
Mapping; Conversion: mark-up to mark-up conversion
Details of further file system functions: techniques for file synchronisation in file systems
Of structured data, e.g. relational data: updating
Computing and data processing
About 11 years 4 months of term left · ends 7 Mar 2038 (estimated)
The following relates generally to importing and verifying the compatibility of files and resources imported using links called by schemas, such as XSD and WSDL.
Currently a business process user who wants to introspect some schemas or definitions, such as XSD, WSDL, etc., which are remote and/or include external references resource links (e.g., imports that include Uniform Resource Links (URLs) that point to resources) provides a set of URLs representing the root resources the user wants to add. Unfortunately, to introduce external schemas to an application a user must manually download and bundle the schemas, and the schema's dependencies, into a file with a particular structure and then import the file. Such a process is extremely cumbersome and inefficient.
As external reference URLs may change unexpectedly, which often “breaks” the resource link, external references could be invalid when called. Because such resources are often called and parsed each time a project or file is loaded, a broken resource link may cause the user's project to fail. In addition, introducing new resources or updating existing ones, could lead to inconsistencies in the project operation.
FIG. 1 is a high level illustration of a system for verifying schema compatibility.
FIG. 2 is pseudo code describing portions of a resource compatibility algorithm for a batch update.
FIG. 3 is pseudo code describing portions of a resource compatibility algorithm for a single update.
FIG. 1 is a high-level block diagram of an exemplary computing system 100 for providing resource verification. Computing system 100 may be any computing system, such as an enterprise computing environment, client-server system, and the like. Computing system 100 includes compatibility verification system 110 configured to process data received from a user interface 114, such as a keyboard, mouse, etc., with regard to verifying and repairing internal and external resource and dependency compatibility, converting, modeling, data binding, maintenance, data elements, information, etc. as described herein.
Note that the computing system 100 presents a particular example implementation, where computer code for implementing embodiments may be implemented, at least in part, on a server. However, embodiments are not limited thereto. For example, a client-side software application may implement compatibility verification system 110, or portions thereof, in accordance with the present teachings without requiring communications between the client-side software application and a server.
In one exemplary implementation, compatibility verification system 110 is connected to display 130 configured to display data 140 (e.g. graphical data), for example, to a user thereof. Display 130 may be a passive or an active display, adapted to allow a user to view and interact with data 140 displayed thereon, via user interface 114. In other configurations, display 130 may be a touch screen display responsive to touches, gestures, swipes, and the like for use in interacting with and manipulating data 140 by a user thereof. Gestures may include single gestures, multi-touch gestures, and other combinations of gestures and user inputs adapted to allow a user to introspect, process, convert, model, generate, deploy, maintain, and update data 140.