Adding RSP package concept thanks to suggestions; also enhancing the wording

1 files changed, 51 insertions, 2 deletions

diff --git a/index.mdwn b/index.mdwn
index cc8ee1d..4b55638 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -3,9 +3,9 @@
 The Resource Sharing Protocol (RSP) is a set of metadata intended to help free software groups
 
 * Share their available resources and also
-* Find groups that can host services for them given their needs and prerequisites. 
+* Find groups that can host services for them given their needs and requirements. 
 
-The RSP splits each resource in a layer or set of service layers. You can think a service layers something very general, comprising from servers, databases, websites. If you need to, you can even consider stuff such as tables and bicycles as layers that provide some kind of service to a hosted group. ;)
+The RSP splits each resource in a layer or set of service layers. You can think of service layers something very general, ranging from servers, databases, websites. If you need to, you can even consider stuff such as tables and bicycles as layers that provide some kind of service to a hosted group. ;)
 
 The core protocol is composed by the following metadata:
 
@@ -67,6 +67,55 @@ The core protocol is composed by the following metadata:
   * Hosting group has legal team/support? 
 * Financial 
 
+# Packages
+
+Even if the metadata supports different configurations, it can be unsuitable to use all set for each application or layer specificiation, especially if you're deadling with multiple layers, one atop of another. Then, it is possible to have a more generic list of prerequisite information, along the lines of a debian package. these are the debian headings:
+
+      Package:
+      State:
+      Automatically installed:
+      Version:
+      Priority:
+      Section:
+      Maintainer:
+      Uncompressed Size:
+      Depends:
+      Suggests:
+      Conflicts:
+      Replaces:
+      Provides:
+      Description:
+
+So possible descriptions for a layer could be something like:
+
+      Package: [generic name/category]{server-vserver}
+      State: [hardware, software, network, labor, physical item]{hardware}
+      Reusable: [limited availability or recurring possibility?]{continuing}
+      Version: [specific 'local' name]{project_name_1.0}
+      Priority: [required/important/standard/optional/extra]{required}
+      Section: [admin/backups/mirrors/doc/comms]{admin}
+      Maintainer: [host/user]{host}
+      Size: [amount or n/a]{10GB}
+      Depends:
+      Suggests: network-traffic (=project_name_*), encryption-policy (=project_name_*),
+         reciprocation-policy (>=1.2)
+      Conflicts: server-*,
+      Replaces: vserver
+      Provides: vserver, server-encryption
+      Description: encrypted vserver
+         This package provides a 10 GB vserver hosted on an
+         individually encrypted single partition. Root administrative
+         access is provided via ssh using key-based authentication, in
+         line with standard encryption policy. Bandwidth can be added
+         by using the network-bw_project_name_* packages.
+
+Where
+
+    key: [text in square brackets] = comment or possible options
+         {text in squiggly brackets} = example
+
+This way, RSP metadata is encapsulated in resource packages that can be announced, distributed or kept for internal use, alowing a given resource to have it's own dependency set and property inheritance.
+
 # Rulesets
 
 It is not strict builtin in the protocol but your group can also adopt internal rules regarding what goes at each layer. As an example, a group can adopt a data persistence rule such as data in a layer with a given level of security cannot be moved to a layer with a lower security level, except in cases it is temporarily or permanently declassified.