This schema defines FDP Manifest At the top level of the Manifest we have four sections: Header, Private, Public and Contents. The Header contains some three elements that can uniquely identify this package (PackageName, Guid, Version) as well as several fields that identify the licensing and compyright status of the contents of the package. The rest of the fields are there to idenify who created the package and when it was made. The buid fields are here to identify when the package was created, not when the package was compiled. The Build number is an integer that is meant to represent the exact build of the package. In the Type field we can record what kinds of modules are contained in the package. The possibilities are source, binary and mixed (both source and binary.) The build target is used to record what target architecture the modules within this package were compiled for. In the creator field, we can record the name, user id, and email address of the person who created this package. In the Modifier field, we can record the name, user id, and email address of the person who changed/updated or modified this package. The name of the company, organization or individual that created or distributes the package. This is the place to record the name and DNS name of the computer on which the package was created. The package may be Debug or Production. We may identify the quality level of the package here. This is the directory, relative to the root of the workspace, where the package will be installed by default. We can track the pakages that this package provides (these are the packages contained in this pacakge.) We also record which packages are required by this package. This is a list of the packages that this package requires to be installed in the workspace for package to function and/or build correctly. In the case of source packages, these are the necessary dependencies for successful build-time operation of the package. For binary packages these dependencies are necessary for successful runtime operation. This tag is used in the Framework Package Database File to track individual package information. The Path is a relative path to the SPD File. The list of dependencies that the package fulfills. This tag is used in the Framework Package Database File to track individual package information. The Path is a relative path to the SPD File. A library. It can be provided by or required by this or other packages. A protocol. It can be provided by or required by this or other packages. The Private section is a place where the files are listed that should not be seen by the users of this package. The Public section is a list of files that are meant to be seen by the users of the package. This is a list of all the files within this package. Each file is identified by its path relative to the workspace root. Specify a filename including the path