System for normalizing and archiving schemas

• US 7,308,458 B2
• Filed: 06/10/2004
• Issued: 12/11/2007
• Est. Priority Date: 06/11/2003
• Status: Active Grant

• Current Assignee: WTVIII, Inc.
• Original Assignee: WTVIII, Inc.
• Inventors: Vincent, III, Winchel Todd
• Primary Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US10/865,529
• Publication Number:
  US 20040268240A1
• Time in Patent Office: 1,279 Days
• Field of Search: 707/100, 707/101, 707/204, 707/102, 707/103.X, 707/103.Y, 707/103.Z, 707/103.R, 707/205, 707/206, 715/513, 715/760
• US Class Current: 1/1
• CPC Class Codes: G06F 16/80 of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML content-based retrieval of web data G06F16/95
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/04812 Interaction techniques based on cursor appearance or behaviour, e.g. being affected by the presence of displayed objects
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/166 Editing, e.g. inserting or deleting
• CPC Class Codes: G06F 40/174 Form filling; Merging
• CPC Class Codes: G06F 40/186 Templates
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71
• CPC Class Codes: G06F 40/226 Validation
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A system for normalizing schemas and for archiving normalized schemas in a schema repository. A schema generator receives user input and creates normalized schemas based on the user input. The normalized schemas are archived in a schema repository that has a directory tree structure that can be searched to retrieve a schema using the schema namespace. Once a schema has been archived in the schema repository, the schema and its namespace preferably are frozen and cannot be altered. Schemas can be reused by searching the schema repository for a schema having a particular namespace, retrieving the archived schema and importing the retrieved schema into a document being created. The system may include multiple schema repositories with identical directory tree structures having identical schemas archived at identical locations in the directory tree structures.

Claims

1. A system for generating normalized mark up language schemas, the system comprising:

a schema generator configured to receive user input and to process the user input in accordance with a predefined schema framework rule set to generate a plurality of normalized mark up language schemas, wherein the normalized mark up language schemas are schemas generated by the schema generator and made to comply with the predefined schema framework rule; and

a first schema repository configured to archive the normalized mark up language schemas and retrieve archived mark up language schemas, the first schema repository having a directory tree structure, and wherein each mark up language schema archived in the first schema repository has a namespace associated with the mark up language schema that points to a location at which the mark up language schema is archived in the first schema repository.

2. The system of claim 1, wherein the first schema repository corresponds to one or more servers located at one or more web addresses, and wherein each schema namespace includes a web address that designates a location of a server at which the mark up language schema associated with the web address is archived.

3. The system of claim 2, wherein each schema namespace also includes a category identifier that identifies a file name in the first schema repository.

4. The system of claim 3, wherein the category identifier identifies a genre to which the mark up language schema associated with the namespace relates.

5. The system of claim 4, wherein the category identifier also identifies a geographical location.

6. The system of claim 2, wherein once a mark up language schema has been archived in the first schema repository, the archived mark up language schema cannot be modified.

7. The system of claim 6, further comprising:

a second schema repository configured to archive mark up language schemas and retrieve archived mark up language schemas, the second schema repository having a directory tree structure, and wherein each mark up language schema archived in the second schema repository has a namespace associated with the mark up language schema that points to a location at which the mark up language schema is archived in the second schema repository, and wherein at least some of the mark up language schemas archived in the first schema repository are also archived in the second schema repository.

8. The system of claim 7, wherein the directory tree structure of the second schema repository is identical to the directory tree structure of the first schema repository, and wherein identical mark up language schemas archived in the first schema repository and in the second schema repository are archived at the same locations in the respective directory tree structures of the first and second schema repositories.

9. The system of claim 7, wherein groups of mark up language schemas stored at certain locations in the first schema repository are copied to certain locations in the second schema repository.

10. The system of claim 1, wherein the first schema repository further comprises:

a user interface configured to receive user input relating to a schema search request to be performed, the first schema repository being configured to search the archives of the first schema repository and retrieve a mark up language schema that matches the search request.

11. The system of claim 1, wherein the schema generator further comprises:

a user interface configured to receive user input and to display information to the user relating to creating, editing and normalizing a mark up language schema.

12. The system of claim 11, wherein if the schema generator determines that a mark up language schema is not normalized, the schema generator processes the mark up language schema to transform the mark up language schema into a normalized mark up language schema.

13. The system of claim 12, wherein the predefined schema framework rule set includes a rule for determining whether a schema namespace is correct.

14. The system of claim 1, further comprising:

a code generator configured to receive a mark up language schema from the schema generator or from the first schema repository and to process the received mark up language schema to generate mark up language instance documents that validate against the received mark up language schema.

15. The system of claim 14, further comprising:

a document repository, wherein the code generator is configured to store the mark up language instance documents in the document repository.

16. The system of claim 15, wherein the code generator is configured to send the mark up language instance documents over a network to an address on the network.

17. The system of claim 15, wherein the network is an Internet, and wherein the schema generator, the first schema repository and the code generator communicate with each other via the Internet.

18. The system of claim 1, wherein the schema generator is also configured to create schema documentation including documenting a history of a mark up language schema over time.

20. The system of claim 1, wherein the schema generator is also configured to package mark up language schemas and publish packaged mark up language schemas.

21. The system of claim 20, wherein the schema generator is also configured to encrypt mark up language schema packages and process encrypted mark up language schema packages.

22. The system of claim 1, further comprising:

crawler logic configured to automatically update the first schema repository.

23. The system of claim 1, wherein the schema generator compares an existing mark up language schema to the predefined schema framework rule set and if the existing mark up language schema complies with the predefined schema framework rule set, the existing mark up language schema is deemed normalized.

19. The system of clam 1, wherein the schema generator is also configured to create one or more data dictionaries.

24. A method for generating normalized-mark up language schemas, the method comprising:

receiving user input and processing the user input in accordance with a predefined schema framework rule set to generate a plurality of normalized mark up language schemas, wherein each normalized mark up language schema complies with the predefined schema framework rule set;

archiving the normalized mark up language schema in a primary schema repository configured to archive normalized mark up language schemas and retrieve normalized mark up language archived schemas, the primary schema repository having a directory tree structure, and wherein each mark up language schema archived in the primary schema repository has a namespace associated with the mark up language schema that points to a location at which the mark up language schema is archived in the primary schema repository.

25. The method of claim 24, wherein the primary schema repository corresponds to one or more servers located at one or more web addresses, and wherein each schema namespace includes a web address that designates a location of a server at which the mark up language schema associated with the web address is archived.

26. The method of claim 24, wherein each schema namespace also includes a category identifier that identifies a file name in the primary schema repository.

27. The method of claim 26, wherein the category identifier identifies a genre to which the mark up language schema associated with the namespace relates.

28. The method of claim 27, wherein the category identifier also identifies a geographical location.

29. The method of claim 24, wherein once a normalized mark up language schema has been archived in the primary schema repository, the archived mark up language schema cannot be modified.

30. The method of claim 24, further comprising:

archiving normalized mark up language schemas in an additional schema repository configured to archive mark up language schemas and retrieve archived mark up language schemas, the additional schema repository having a directory tree structure, and wherein each mark up language schema archived in the additional schema repository has a namespace associated with the mark up language schema that points to a location at which the mark up language schema is archived in the additional schema repository, and wherein at least some of the mark up language schemas archived in the primary schema repository are also archived in the additional schema repository.

31. The method of claim 30, wherein the directory tree structure of the additional schema repository is identical to the directory tree structure of the primary schema repository, and wherein identical mark up language schemas archived in the primary schema repository and in the additional schema repository are archived at the same locations in the respective directory tree structures of the primary and additional schema repositories.

32. The method of claim 24, wherein if a determination is made that a mark up language schema is not normalized, transforming the mark up language schema into a normalized mark up language schema.

33. The method of claim 32, wherein the predefined schema framework rule set includes a rule for determining whether a schema namespace is correct.

34. A computer program for generating normalized-mark up language schemas, the computer program being recorded on a computer-readable medium, the program comprising:

a first code segment for processing user input in accordance with a predefined schema framework rule set to generate a plurality of normalized mark up language schemas that comply with the predefined schema framework rule set; and

a second code segment for causing the normalized mark up language schemas to be archived in a primary schema repository configured to archive mark up language schemas, the primary schema repository having a directory tree structure, and wherein each mark up language schema archived in the primary schema repository has a namespace associated with the mark up language schema that points to a location at which the mark up language schema is archived in the primary schema repository.

35. The computer program of claim 34, further comprising a third code segment for comparing an existing mark up language schema with the predefined schema framework rule set to determine whether the existing mark up language schema complies with the rule set, wherein if the existing mark up language schema complies with the predefined schema framework rule set, the existing mark up language schema is deemed normalized.

36. The computer program of claim 35, wherein if the third code segment determines that the existing mark up language does not comply with the predefined schema framework rule set, the third code segment transforms the existing mark up language schema into a normalized mark up language schema.