RPS Structure and Linking Discussion

Please use this page for discussion. Do not delete other authors entries, but feel free to comment. When mature, this should become part of the story boards and business requirements. Use the signature --~~~~ to mark your own text.

File and Folder Rules

• File and folder specifications would aid in converting RPS messages into NeES-like submissions --Joelfinkle 22:33, 16 July 2009 (UTC)
• This should be left up to the individual regulators, and is out of scope for the RPS message --Joelfinkle 22:33, 16 July 2009 (UTC)

Hyperlinking

• Eliminating between-document hyperlinking would eliminate any need to specify file and folder structure --Joelfinkle 22:33, 16 July 2009 (UTC)
• Eliminating between-document hyperlinking would slow down review --Joelfinkle 22:33, 16 July 2009 (UTC)
• Between-submission-unit hyperlinking currently requires that assembly tools "know" how submission units are stored relative to each other. --Joelfinkle 22:33, 16 July 2009 (UTC)
• Most proposed solutions to reroute "broken" or "updated" links would require Acrobat plug-ins or server-side redirectors, which is out of scope for the RPS project -- we can create specifications, but not enforce them. --Joelfinkle 22:33, 16 July 2009 (UTC)
• One alternative would be that the RPS message must include all between-document link information, so that a review system can construct the necessary links. This would remove the need for betweee-document links in the documents themselves, but would still require the review system to have enhancements. --Joelfinkle 22:33, 16 July 2009 (UTC)