Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Efficient Processing of Policy Meta Data

IP.com Disclosure Number: IPCOM000020806D
Original Publication Date: 2003-Dec-15
Included in the Prior Art Database: 2003-Dec-15
Document File: 1 page(s) / 5K

Publishing Venue



Policies can be logically grouped for efficient storage, retrieval, and deployment. It is important to know statistics about the policies within each logical group. Examples include: 1) The number of policies within this group, 2) the overall status of the group such as draft, publish, deployed, 3) who last modified any policy within this group, and 4) when was the last modification was made to any policy within this group. To determine these statistics by examining each policy within the logical group is expensive, especially when there are very large numbers of policies. This publication discloses a process to efficiency handle this meta data.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 71% of the total text.

Page 1 of 1

Efficient Processing of Policy Meta Data

Meta data is stored along with the policies in this logical group. For example, if this logical group is a single XML document that contains all of the policies for this logical group, the metadata could be stored within a high level XML tag.

As the policies are being added, changed, deleted to this logical group, the meta data is updated reflecting the latest changes to this logical group of policies.

When this logical group is retrieved, just the metadata needs to be analyzed to determine the information as described in 1. That is, every policy within this logical group does not need to be analyzed to determine the statistics as described in 1.

Policy documents that are related could be stored in a single XML document. As the policies are being added, changed, deleted, deployed/undeployed into production, the metadata XML tag would also be updated. For example, if a policy is added to the XML document, the metadata tag would be retrieved, the counter for the number of policies would be retrieved, incremented by one, and stored back into the metadata XML tag, along with the time-stamp and who made this change.

Later when, this XML policy document is retrieved, only the metadata tag needs to be retrieved, in order to display the number of policies contained in the XML policy document. This saves the retrieving program from having to look for each policy within this XML policy document and counting the number of policies co...