Hi guys – this is some
input from Dan and me on adding typed metadata to SPML. Our thinking is to add
more strictly defined operational metadata that can be used, for example, for
auditing and compliance purposes.
-
All requests can
have the typed metadata linked to it. The schema for the metadata is defined at
the system level rather than at the object level.
o
As an example,
things like first name and last name would be fields defined on the user
schema, just name and members are attributes on a group. But a
metadata attribute like “sox related” can be tagged on to any
object in the system without having to define it in the object’s schema
-
The metadata could
also describe the “flow” of a request, e.g. tagging a request as
“high-priority”
-
The main consumer of
the metadata tags are things like policies. For example, a workflow
interface can use a special sox-approval process for any request for a system
or role containing the sox related tag in the metadata
-
Reporting and compliance/separation-of-duties
can also leverage the metadata
Richard Sand | CEO
239 Kings Highway East | Haddonfield | New Jersey 08033 | USA
Mobile: +1 267 984 3651| Office: +1 856 795 1722| Fax: +1 856 795 1733
