Issue 7764: Provide standard means of identifying manifests                                                                                                                                                         (ras-ftf)
Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com)
Nature: Uncategorized Issue
Severity: 
Summary: The statement in 2.3 1 of RFC "it is up to any tool or the user to
determine which files in the package are manifest files and which are
artifacts of the asset." is unacceptable for interchange purposes
Resolution: 
Revised Text: Resolution:
For bundled assets in a .ras file: Use "manifest.rmd" for the manifest file name
For unbundled assets (i.e., not in a .ras file): Use <any>.rmd for the manifest file name
You may also include <any>.rmd in a bundled .ras file, but the manifest.rmd file is the entry point.
Update the RAS 2.0 final document to reflect this clarification.

Actions taken:
September 20, 2004: received issue
August 1, 2005: closed issue
Discussion: 

End of Annotations:=====
6. Provide standard means of identifying manifests
The statement in 2.3 1 of RFC "it is up to any tool or the user to
determine which files in the package are manifest files and which are
artifacts of the asset." is unacceptable for interchange purposes