This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Regulated Activity Structure Hierarchy"
Jump to navigation
Jump to search
Joelfinkle (talk | contribs) (New page: The Regulated Activity Structure Hierarchy (RASH) is a proposed structured document format to accompany Regulated Product Submissions (RPS). It is designed to be a ''machine-readable i...) |
Joelfinkle (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The Regulated Activity Structure Hierarchy (RASH) is a proposed structured document format to | + | The Regulated Activity Structure Hierarchy (RASH) is a proposed structured document format that would be an adjunct to the [[Regulated Product Submissions]] (RPS) standard. |
| − | It is designed to be a ''machine-readable implementation guide'' connecting the controlled vocabularies and how they are organized into a set for a given submission type. | + | It is designed to be a ''machine-readable implementation guide'' connecting the controlled vocabularies and how they are organized into a set for a given submission type. One RASH document would be used for each submission type in viewing and assembly tools to create the hierarchical view of the submission. |
| − | The Scope Statement is under review at this time | + | * The Scope Statement is under review at this time: [[Image:RASH_Project_Scope_Statement_20091214.doc|Scope Statement in MS Word]] |
| − | A Presentation on the subject was given at the January 2010 Workng Group Meeting in Phoenix. | + | * A Presentation on the subject was given at the January 2010 Workng Group Meeting in Phoenix. [[Image:RASH_Proposal_Overview.pdf|RASH Overview Slides]] |
Latest revision as of 17:32, 28 January 2010
The Regulated Activity Structure Hierarchy (RASH) is a proposed structured document format that would be an adjunct to the Regulated Product Submissions (RPS) standard. It is designed to be a machine-readable implementation guide connecting the controlled vocabularies and how they are organized into a set for a given submission type. One RASH document would be used for each submission type in viewing and assembly tools to create the hierarchical view of the submission.
- The Scope Statement is under review at this time: File:RASH Project Scope Statement 20091214.doc
- A Presentation on the subject was given at the January 2010 Workng Group Meeting in Phoenix. File:RASH Proposal Overview.pdf
