- Joined
- May 10, 2007
- Messages
- 8,762
Foundational Knowledgebase – Work Product Content Parameters
Forward
This message is the third in a series of eight related to the Mission Advancement Framework. For proper context be sure to read the previous messages found here:
Step 1: http://www.ronpaulforums.com/showth...n-Advancement-Framework-A-new-site-initiative!
Step 2: http://www.ronpaulforums.com/showthread.php?490665-Parameters-of-the-Mission-Advancement-Framework
The complete outline of the steps is listed below, these will be released in an orderly fashion. Steps will be released one at a time to allow focusing on one point, to allow for community discussion and to establish points that may alter the start of the next step.
The objective of this message is to establish the parameters of the content of the final work product of the Foundational Knowledgebase, part of the previously mentioned “prerequisite goal”. These parameters are subject to debate and subsequent change to achieve the best path forward.
Mission Advancement Framework – Roadmap to Success
Step 1: Introduction of the Mission Advancement Framework, establishment of initial goals.
Step 2: Parameters of the Mission Advancement Framework. Part of the “prerequisite goal”.
Step 3: Parameters of the content of the final work product of the Foundational Knowledgebase. Part of the “prerequisite goal”.
Step 4: Parameters of the organizational structures used for developing the Foundational Knowledgebase. Part of the “prerequisite goal”.
Step 5. Setting a strategy to achieve Goal 1.
Step 6: Setting a strategy to achieve Goals 2.
Step 7: Setting a strategy to achieve Goal 3.
Step 8: Setting a strategy to achieve Goal 4.
Foundational Knowledgebase - Information Organization
In a somewhat chicken-and-egg situation, in order to take steps towards the developed of proper tools and tactics we need to use effective tools and tactics. To resolve this dilemma, the first effort will be to develop a set of design objectives for the developed of the Foundational Knowledgebase. These design objectives can provide later value for the MAF.
Design objectives are broken down into the organization of information and people, per the scope of the MAF.
Design Objectives for the Organization of Information
The follow design objectives are being proposed to organize information within the Foundational Knowledgebase:
• Have established content guidelines.
• Provide facilities and solutions to manage internal division of desired content.
• Establish parameters for the way the Foundational Knowledgebase will be published.
• Characterize a suitable publishing system.
Proposals for these design objectives is discussed below.
Content Guidelines for the Foundational Knowledgebase
For the final work product to be effective there has to be specific Content Guidelines defined and followed. The Content Guidelines will have two components, the first being the current “Core content policies” of Wikipedia and the second being additional site specific Content Guidelines. The site specific Content Guidelines are as follows:
• All work should apply logical deduction to arrive at conclusions.
• All work shall aim to develop important principles that are highlighted within the work.
• All work shall adhere to a predefined outline of section content.
• All work shall follow a uniformed standard of linguistics, which is to be developed.
• Key work products and the development of principles should not reply upon the use of current issues that commonly change with time.
• The core of the Foundational Knowledge will be completely objective but some sections can be subjective. Subjective sections should be clearly marked.
• All works shall be devoid of logical fallacies or what could be viewed as propaganda.
• All work should reference to larger, external bodies of work for efficiency.
• Proper attributes should be included as needed.
• All works can provide information on donating to the author or the Foundational Knowledge. [Credit to site member Xerographica for this idea]
• All work shall adhere to our site Usage Guidelines.
These guidelines are subject to future refinement.
Managing Internal Division of Desired Content
There are many cases where individuals who support our Mission have different viewpoints on philosophical and tactical issues. The Foundational Knowledge does not have to draw conclusions when there is no logically provable correct way and can support the content of each viewpoint in an equal manner. In this way not everyone has to agree on all philosophical or tactical issues.
Section Classifications & Attributes
Each section will be categorized in one of the following classifications, each of which has different attributes. The section types and attributes are as follows:
Foundational: Focuses on the end goal of the development of principles in a clear, concise and effective manner. Foundational Sections must be objective, will be multi-author and may be updated frequently. Note: Donations to Foundational Sections will go to support future MAF efforts.
Value-add: Value-add sections can present arguments from a particular set of convictions. Value-add pieces can provide more in-depth characterizations, go into concrete details of specific events and describe more dynamics that are typical in a political piece. Value-add sections can have a singular author and be closed to editing from other authors.
Note: Donations to Value-add Sections will go to the author or to support future MAF efforts, based on the authors’ choice. If the author abandons the property, then further donations will go to support future MAF efforts.
Organizational: Some sections may exist to provide navigational assistance. These sections will be owned and controlled by the MAF administration.
Foundational Knowledgebase Administration: Some sections may exist to help support the development of the Foundational Knowledgebase. These sections will be owned and controlled by the MAF administration.
Publishing System for the Foundational Knowledgebase
All content will be contained within a web based Content Management System (CMS) that is the best fit for the purpose. The system shall include revision control such that all past versions of a sections content can be retrieved.
Data obtained for Goal #2 shall be stored in a database with a “strongly typed” data model which will allow for data to be searched for, filtered and ordered based on various data attributes.
Forward
This message is the third in a series of eight related to the Mission Advancement Framework. For proper context be sure to read the previous messages found here:
Step 1: http://www.ronpaulforums.com/showth...n-Advancement-Framework-A-new-site-initiative!
Step 2: http://www.ronpaulforums.com/showthread.php?490665-Parameters-of-the-Mission-Advancement-Framework
The complete outline of the steps is listed below, these will be released in an orderly fashion. Steps will be released one at a time to allow focusing on one point, to allow for community discussion and to establish points that may alter the start of the next step.
The objective of this message is to establish the parameters of the content of the final work product of the Foundational Knowledgebase, part of the previously mentioned “prerequisite goal”. These parameters are subject to debate and subsequent change to achieve the best path forward.
Mission Advancement Framework – Roadmap to Success
Step 1: Introduction of the Mission Advancement Framework, establishment of initial goals.
Step 2: Parameters of the Mission Advancement Framework. Part of the “prerequisite goal”.
Step 3: Parameters of the content of the final work product of the Foundational Knowledgebase. Part of the “prerequisite goal”.
Step 4: Parameters of the organizational structures used for developing the Foundational Knowledgebase. Part of the “prerequisite goal”.
Step 5. Setting a strategy to achieve Goal 1.
Step 6: Setting a strategy to achieve Goals 2.
Step 7: Setting a strategy to achieve Goal 3.
Step 8: Setting a strategy to achieve Goal 4.
Foundational Knowledgebase - Information Organization
In a somewhat chicken-and-egg situation, in order to take steps towards the developed of proper tools and tactics we need to use effective tools and tactics. To resolve this dilemma, the first effort will be to develop a set of design objectives for the developed of the Foundational Knowledgebase. These design objectives can provide later value for the MAF.
Design objectives are broken down into the organization of information and people, per the scope of the MAF.
Design Objectives for the Organization of Information
The follow design objectives are being proposed to organize information within the Foundational Knowledgebase:
• Have established content guidelines.
• Provide facilities and solutions to manage internal division of desired content.
• Establish parameters for the way the Foundational Knowledgebase will be published.
• Characterize a suitable publishing system.
Proposals for these design objectives is discussed below.
Content Guidelines for the Foundational Knowledgebase
For the final work product to be effective there has to be specific Content Guidelines defined and followed. The Content Guidelines will have two components, the first being the current “Core content policies” of Wikipedia and the second being additional site specific Content Guidelines. The site specific Content Guidelines are as follows:
• All work should apply logical deduction to arrive at conclusions.
• All work shall aim to develop important principles that are highlighted within the work.
• All work shall adhere to a predefined outline of section content.
• All work shall follow a uniformed standard of linguistics, which is to be developed.
• Key work products and the development of principles should not reply upon the use of current issues that commonly change with time.
• The core of the Foundational Knowledge will be completely objective but some sections can be subjective. Subjective sections should be clearly marked.
• All works shall be devoid of logical fallacies or what could be viewed as propaganda.
• All work should reference to larger, external bodies of work for efficiency.
• Proper attributes should be included as needed.
• All works can provide information on donating to the author or the Foundational Knowledge. [Credit to site member Xerographica for this idea]
• All work shall adhere to our site Usage Guidelines.
These guidelines are subject to future refinement.
Managing Internal Division of Desired Content
There are many cases where individuals who support our Mission have different viewpoints on philosophical and tactical issues. The Foundational Knowledge does not have to draw conclusions when there is no logically provable correct way and can support the content of each viewpoint in an equal manner. In this way not everyone has to agree on all philosophical or tactical issues.
Section Classifications & Attributes
Each section will be categorized in one of the following classifications, each of which has different attributes. The section types and attributes are as follows:
Foundational: Focuses on the end goal of the development of principles in a clear, concise and effective manner. Foundational Sections must be objective, will be multi-author and may be updated frequently. Note: Donations to Foundational Sections will go to support future MAF efforts.
Value-add: Value-add sections can present arguments from a particular set of convictions. Value-add pieces can provide more in-depth characterizations, go into concrete details of specific events and describe more dynamics that are typical in a political piece. Value-add sections can have a singular author and be closed to editing from other authors.
Note: Donations to Value-add Sections will go to the author or to support future MAF efforts, based on the authors’ choice. If the author abandons the property, then further donations will go to support future MAF efforts.
Organizational: Some sections may exist to provide navigational assistance. These sections will be owned and controlled by the MAF administration.
Foundational Knowledgebase Administration: Some sections may exist to help support the development of the Foundational Knowledgebase. These sections will be owned and controlled by the MAF administration.
Publishing System for the Foundational Knowledgebase
All content will be contained within a web based Content Management System (CMS) that is the best fit for the purpose. The system shall include revision control such that all past versions of a sections content can be retrieved.
Data obtained for Goal #2 shall be stored in a database with a “strongly typed” data model which will allow for data to be searched for, filtered and ordered based on various data attributes.