Search
Subscribe

Bookmark and Share

About this Blog

As enterprise supply chains and consumer demand chains have beome globalized, they continue to inefficiently share information “one-up/one-down”. Profound "bullwhip effects" in the chains cause managers to scramble with inventory shortages and consumers attempting to understand product recalls, especially food safety recalls. Add to this the increasing usage of personal mobile devices by managers and consumers seeking real-time information about products, materials and ingredient sources. The popularity of mobile devices with consumers is inexorably tugging at enterprise IT departments to shifting to apps and services. But both consumer and enterprise data is a proprietary asset that must be selectively shared to be efficiently shared.

About Steve Holcombe

Unless otherwise noted, all content on this company blog site is authored by Steve Holcombe as President & CEO of Pardalis, Inc. More profile information: View Steve Holcombe's profile on LinkedIn

Follow @WholeChainCom™ at each of its online locations:

« Elastic Tag Mapping and Data Ownership | Main | Personal Health Records, Data Portability and the Continuing Privacy Paradigm »
Friday
May232008

US Patent 5,418,957: Network data dictionary (Narayan)

Title: Network data dictionary
Patent Number: US Patent 5,418,957
Issued: May 23, 1995
Filed: March 9, 1992
Parent case: n/a
Inventor(s): Narayan, Rom
Assignee: n/a
Referenced at issuance: US Patent 5,008,853 (Xerox Corporation) Φ
Referenced after issuance: US Patent 5,764,973 (enterWorks.com)
Blogger comment:

There were 9 references to prior patents at issuance, including US Patent 5,008,853, referenced above. The remaining references are unremarkable for the scope and purposes of this blog.

An advanced search at USPTO online on May 16, 2008 for distinguishing references to this patent after its issuance using ref/5418957 reveals 36 references. A more refined search reveals US Patent 5,764,973.

Abstract:

The Network Data Dictionary is a device for enabling standardization of data structures in programs, file layouts and Data Base Management System (DBMS) schema residing in Include Files located on one or more computers in a network. By making the data structures comply with the data element definitions stored in a common data element dictionary, improvements in the quality, accuracy, and consistency of data can be obtained, while simultaneously providing productivity advantages to programmers.

Independent claims (as numbered):

1. In a network of one or more computers having data structures relating to programs, file layouts, and database schema, the data structures being stored in Include Files, wherein each of the data structures comprises one or more data items, each of the Include Files is associated with a Support File, and each of the Include Files is accessible from an Include File Dictionary (IFD) that includes a tree-structured directory for mapping the Include Files to the network and access control information, a method for enabling a user to interactively edit or create Include Files so as to comply with a set of logical data element definitions derived from the data structures and stored in a Data Element Dictionary (DED), the method comprising the steps of:

1) retrieving a user selected Include File from the IFD into a text editor;

2) editing or creating data structures of the selected Include File from the text editor;

3) validating a user selected data item of the data structures against the logical data element definitions in the DED from the text editor, and if valid logical data element definitions for the selected data item exist, performing the steps of:

displaying logical data element definitions that are valid for the selected data item;

replacing the selected data item in the text editor with a user selected one of the displayed logical data element definitions;

storing cross-reference information in a Support file corresponding to the selected Include File, the cross-reference information referencing a logical data element definition in the DED corresponding to the selected data item in the text editor; or

if valid logical data element definitions for the selected data items do not exist, performing the steps of:

proposing a logical data element definition by the user, in accordance with a set of rules of defined in the DED, in the DED and subject to approval by a system administrator;

replacing the selected data item in the text editor with the proposed logical data element definition;

4) auditing the selected Include File using the support file, including cross-references, and calculating a dictionary compliance percentage to provide a summary of the compliance of the selected Include File to the DED.  

PrintView Printer Friendly Version

EmailEmail Article to Friend

References (1)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>