I just read this thread and had to jump in and emphasize the motivation for supporting the modularity of the data structures. There will be as many data and messaging requirements as there are regulatory domains, device standards, and maybe even database administrators. If PAWS were to focus on providing a messaging capability rather than specifying which messages must be used in a transaction it will be much easier. When a device contacts a database it would learn or confirm which regulatory domain it is in, what messaging is required, and what data requirements are necessary. The basics of a device having to contact a DB and its use being contingent on a list from the DB will be there but the specifics about the negotiation to get that approval and to keep it can be different. Seeking this sort of loose coupling for PAWS will make this protocol much more versatile over time.
John _______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
