This include requiring or relying on specific functionality from one or more of the following: Transport (ex: SOAP conventions) SIS Functional Profiles Identity Management Profiles Global Data Model Metadata Central Administration or Smart Zone Zone Services (ex: Assessment) Proposed new Object, Infrastructure or Specifics of dependency Element or Attribute International technology dependency 5 Detailed Design Place the detailed element by element, attribute by attribute breakdown of the Data Model Extension here. This work is normally done by members of the assigned Project Team. The possible values of the column include “Char” One of the following characteristics: M Mandatory. Item must appear in every Add Event and Response message for the object – ReQuired. Item must either appear in an Add Event or eventually be included in a Change Event. Q – S Supported. Item may or may not appear in any message relating to the object. However if its – is supplied / available, it must be included by the sender in Event and Response messages. C Conditional. Item is required if the included conditions are satisfied – O Optional. Item may or may not appear in any message relating to the object. It need not be – supported by the sender Plus one or more of the following characteristics if applicable: I Immutable. Item value cannot be changed once supplied. – U Unique. Item value is unique from all other objects containing that item (ex: RefId) – Item may not be used in a Request message. This would be true for elements N Non-Queryable. – which might be calculated by the object provider (ex: aggregates) Plus the following characteristic if applicable: R Repeatable. Item may appear more than one time. – The of each item is either an XML type (ex: integer) or a named SIF Global Type. “type” XML Facets can help to further define the value of an item. These can include length, range, and per-type value restrictions. They should be specified if known.
This include requiring or relying on specific functionality from one or more of the following: Transport (ex: SOAP conventions) SIS Functional Profiles Identity Management Profiles Global Data Model Metadata Central Administration or Smart Zone Zone Services (ex: Assessment) Proposed new Object, Element or Attribute Infrastructure or International technology dependency Specifics of dependency 5 Detailed Design Place the detailed element by element, attribute by attribute breakdown of the Data Model Extension here. This work is normally done by members of the assigned Project Team. The possible values of the “Char” column include One of the following characteristics: M – Mandatory. Item must appear in every Add Event and Response message for the object Q – ReQuired. Item must either appear in an Add Event or eventually be included in a Change Event. S – Supported. Item may or may not appear in any message relating to the object. However if its is supplied / available, it must be included by the sender in Event and Response messages. C – Conditional. Item is required if the included conditions are satisfied O – Optional. Item may or may not appear in any message relating to the object. It need not be supported by the sender Plus one or more of the following characteristics if applicable: I – Immutable. Item value cannot be changed once supplied. U – Unique. Item value is unique from all other objects containing that item (ex: RefId) N – Non-Queryable. Item may not be used in a Request message. This would be true for elements which might be calculated by the object provider (ex: aggregates) Plus the following characteristic if applicable: R – Repeatable. Item may appear more than one time. The “type” of each item is either an XML type (ex: integer) or a named SIF Global Type. XML Facets can help to further define the value of an item. These can include length, range, and per-type value restrictions. They should be specified if known.
DMEP%20Assessment%20admin%20and%20session%20objects_final.docx