[
Lists Home |
Date Index |
Thread Index
]
At 13:52 29/10/2003, Chiusano Joseph wrote:
>Earlier this year, the U.S. Federal CIO Council conducted an "E-Forms
>for E-Gov" pilot in which I participated (PureEdge did as well). One of
>the points that was brought out in Section 6.7 (Archival Records Domain)
>of the final report [1] was the importance of binding together
>presentation, content, and context:
>
><Quote>
>Briefly, the National Archives and Records Administration (NARA)
>guidlines require that the "presentation", "content", and "context" must
>be bound together in such a way that they can be demonstrated to belong
>to the same transaction. This may mean physically combining these into a
>single physical file, or ensuring that they are bound together through
>some other trusted means, such as electronic hashes and signatures. In
>addition, any signature must be applied to this combination of
>presentation, content, and context, and the authentication process must
>ensure integrity.
>
>For most government applications, E-Forms solutions must be designed and
>selected with these core archival requirements in mind.
></Quote>
I wonder how that aligns with the 508 accessibility requirements?
Or do we assume that all electronic forms are accessible.
I wonder if that was addressed by the pilot.
regards DaveP
|
