|A Vision for Open Hypermedia Systems||Nürnberg and Leggett|
One complication in this layer is that the set of abstractions that the Sproc Specific Layer presents to its clients is open. It cannot be the case that the SG layer be expected to be able to translate arbitrary structural abstractions into generic structure objects. To remedy this, each instance of a Sproc Specific layer protocol is expected to be expressed in terms of generic structure objects when the services of the SG Layer are invoked.
Since the Sproc Generic Layer must already express its abstractions in terms of generic structure objects, the SG Layer need not do any translation. This raises the question of why the SG layer exists at all. This is because there are some aspects of OHP messages that are common to all Sproc Specific Layers. This common functionality is encapsulated in the SG layer. This functionality involves tagging messages with standard "header" type information. This information has been the subject of several posts to the OHS mailing list, including Nürnberg's 8 June post and Reich's 9 June post.
What information should be considered "header" information? Basically, the criterion is that it be applicable to OHP messages independent of the particular Sproc and structural abstractions handled by the messages. Working from the previous OHS list posts, we propose the following header information:
Details as to the data types and representations of these types are provided in Appendix B.
2. Scope of the OHSWG...
4. An OHS Reference Architecture Proposal...
5. An OHP Proposal...
Appendix A. Generic Encoding Layer Rules
Appendix B. Sproc Generic Layer Rules
Appendix C. Sproc Specific Layer Rules
Appendix D. Sproc Interface Format
Appendix E. Current Protocol Proposal in Sproc Interface Format
Peter J. Nürnberg, John J. Leggett