At 04:31 PM 8/15/2003, Pete (Madscientist) wrote:
ASRG folks,
I have started a web site for the development of an XML based CPDL
(Consent Policy Description Language).
I have also posted a boilerplate example that we can refine until we are
happy with it. I know there are a number of examples and notes that are
missing from the boilerplate. I will review the archives and "massage
them in" to the example document as I have time - I am out of time for
today.
The site is at the following URL.
Comments are strongly encouraged.
http://www.sortmonster.com/ASRG/
Any particular reason why the implementation specific details are included
within the same XML files? Consent policies will need to be
implementation-independent and it might be a good idea to split them up
into two XML files. This is similar to the way the J2EE platform handles
deployment - two XML files are provided, one vendor and implementation
neutral, and the second implementation-specific.
Also, do we need to include the identification of the person or system that
the policy applies to?
Yakov
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg