Neither the process steps which indicate how an agent can declare itself as a supplier or user of Zone Services, nor the process steps which allow the ZIS to recognize such declarations have been included in the SIF_Provision process flow logic.

For this initial release of Zone Services, the preset ACL tables in all ZIS-certified products which are currently used to limit the rights of applications with respect to object provisioning and subscription MUST be extended to include the application rights with regards to Zone Services provisioning as well.

Instead of specifically asserting those rights in the Provision method, Zone Services and clients of Zone Services MUST rely on preset ACLs within the ZIS to authorize them. These are retrievable through the “SIF_RequestService and SIF_SubscribeService elements of the SIF_AgentACL object.

An additional ZIS messaging check during SIF_Request handling is required. If none of the SIF_Request/SIF_Version elements are supported by the provider/responder, even using wildcard matching, an appropriate error " Request and Response/7 -- Responder does not support requested SIF_Version" must be returned by the ZIS.

Step 2 mistakenly assumes all SIF_Requests are SIF_Query-based. This ignores the possibility that the request could be a SIF_ExtendedQuery, which also must be handled by the receiving ZIS.

As non-queued messages, step 6 in each process flow should indicate that if a failure to reach the Push-mode agent occurs, a SIF_LogEntry be published.

The rule that “only one service provider per zone may publish notifications for that service into the zone” is not documented in the SIF_ServiceNotify process flow.

The second paragraph should be deleted. The value of this element should be NULL if no predecessor item exists.

There is an element in the published DisciplineIncident object called ActionList. This element has a type = 'List.' Since the SIF Data Model currently supports two list types called List and ActionList this resulted in an element called ActionList and a type called ActionList, further confused by the fact that the element ActionList is of type List.

The solution mandated that the element name be changed. IncidentActionList/Action is now IncidentActionList/IncidentAction.

The wording in the 2nd paragraph should now read as follows "Note there is only one current home enrollment at a time for a student. One and only one instance of the StudentSchoolEnrollment object must exist for a given student with MembershipType=Home for the time interval between EntryDate and ExitDate, inclusive."

SIF_PacketNumber is a positiveInteger for both these messages as opposed to an unsignedInt. This has been corrected in the XSD.

There is an apparent spec/schema error in 5.3.3 SIF_ZoneStatus that throws off .NET XML serialization resulting from the schema. Specifically Service_Requesters is defined as OR, as is child element Service_Requester.

Service_Requesters has been redefined as optional (O), since all the other similar related zone service additions - Service_Providers, Service_Responders, Service_Subscribers are optional. Service_Requesters and other child repeatable elements have been redefined as MR. This has been corrected in the XSD.

Both these objects should have a composite primary key consisting of @SchoolInfoRefId and @Date. The Date has been omitted. This has been corrected in the XSD.

The Agency Identifier Service RequestIdentifierResponse message was missing an outer “Match” element. This meant it would only support one ambiguous match per packet. This has been corrected in the XSD.

The exhibit below shows the updated portion of the Specification related to this errata item.