This document is also available in these non-normative formats: ZIP archive, PDF (for printing as a single file), Excel spreadsheet.
Copyright ©2023 Systems Interoperability Framework (SIF™) Association. All Rights Reserved.
SIF is not a product, but a technical blueprint for enabling diverse applications to interact and share data related to entities in the pK-12 instructional and administrative environment. SIF is designed to:
The SIF Implementation Specification defines common data formats and rules of interaction and architecture, and is made up of two parts:
SIF Infrastructure defines;
The Schools Interoperability Framework Association (SIF Association); also known as; the Systems Interoperability Framework Association outside North America, doing business as Access 4 Learning (A4L) Community, is an industry initiative to enable interoperability and data sharing between software applications in the pK-12 instructional and administrative environment, and the forum for companies and educators to participate in the development of SIF specifications in the SIF Association's working groups and task forces. The SIF Association is designed to:
The information, software, products, and services included in the SIF Implementation Specification may include inaccuracies or typographical errors. Changes are periodically added to the information herein. The SIF Association may make improvements and/or changes in this document at any time without notification. Information contained in this document should not be relied upon for personal, medical, legal, or financial decisions. Appropriate professionals should be consulted for advice tailored to specific situations.
THE SIF ASSOCIATION, ITS PARTICIPANT(S), AND THIRD PARTY CONTENT PROVIDERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, TIMELINESS, AND ACCURACY OF THE INFORMATION, SOFTWARE, PRODUCTS, SERVICES, AND RELATED GRAPHICS CONTAINED IN THIS DOCUMENT FOR ANY PURPOSE. ALL SUCH INFORMATION, SOFTWARE, PRODUCTS, SERVICES, AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. THE SIF ASSOCIATION AND/OR ITS PARTICIPANT(S) HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION, SOFTWARE, PRODUCTS, SERVICES, AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT.
IN NO EVENT SHALL THE SIF ASSOCIATION, ITS PARTICIPANT(S), OR THIRD PARTY CONTENT PROVIDERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA, OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OR PERFORMANCE OF THIS DOCUMENT, WITH THE DELAY OR INABILITY TO USE THE DOCUMENT, THE PROVISION OF OR FAILURE TO PROVIDE SERVICES, OR FOR ANY INFORMATION, SOFTWARE, PRODUCTS, SERVICES AND RELATED GRAPHICS OBTAINED THROUGH THIS DOCUMENT OR OTHERWISE ARISING OUT OF THE USE OF THIS DOCUMENT, WHETHER BASED ON CONTRACT, TORT, STRICT LIABILITY, OR OTHERWISE, EVEN IF THE SIF ASSOCIATION, ITS PARTICIPANT(S), OR THIRD PARTY CONTENT PROVIDERS HAVE BEEN ADVISED OF THE POSSIBILITY OF DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IF YOU ARE DISSATISFIED WITH ANY PORTION OF THIS DOCUMENT OR WITH ANY OF THESE TERMS OF USE, YOUR SOLE AND EXCLUSIVE REMEDY IS TO DISCONTINUE USING THIS DOCUMENT.
This specification is released with the following provisos to developers and educators.
Though a product may be demonstrated to comply with this specification, no product may be designated as SIF Certified™ by an organization or individual until the product has been tested against and passed established compliance criteria, published separately [SIFCertification]. Organizations and individuals that are currently paying annual membership dues to the SIF Association and dedicating resources to the initiative may also use the designation SIF Participant to describe their involvement with the SIF Association and SIF in marketing, public relations and other materials.
Copyright© SIF Association (2011-2023). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the SIF Association, or its committees, except as needed for the purpose of developing SIF standards using procedures approved by the SIF Association, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the SIF Association or its successors or assigns.
With respect to this SIF Specification, decision makers are typically interested in the capabilities and designs largely present in the Base Architecture volume. This document, the SIF Infrastructure Specification, contains an Infrastructure section describing the payloads used in a format that should not be a barrier to readers with a some knowledge of [XML]. More technical readers, including software architects, developers and integrators, will also be interested in all the separate Infrastructure volumes.
The first time a term or concept is defined, it may be emphasized.
SIF message and object names, XML element tags, attribute names and values, and other codes or values are typically presented as in this sentence.
References to other works occurring in this text are given in brackets, e.g. [REFERENCE]. The text in brackets corresponds to a key in the References appendix. Often when the text in the brackets duplicates surrounding text, the reference alone is used (e.g. [XML] instead of XML [XML]).
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, OPTIONAL, when EMPHASIZED, are to be interpreted as described in [RFC 2119].
Quick overviews of XML structures, including messages, objects, common elements and types, are provided in XML diagrams. The following diagram illustrates the conventions typically encountered in SIF.
XML elements are represented by rectangles with the name of the element in the upper portion and the type, if any, in the lower portion. Attributes
are represented in the same fashion, but have an @
icon rather than a SIF icon. Elements and attributes that are optional have a circled ?
(0 or 1 occurrence) to the left of the rectangle. Optional and mandatory repeatable elements are indicated by a circled *
(0 or more occurrences)
and +
(1 or more occurrences), respectively.
Element attributes are grouped together in a rectangular block and connected to the element with a line that turns at right angles.
Ordered sequences of XML elements are bracketed by lines that turn at right angles. When a choice of XML elements is indicated, the elements are bracketed by angled
lines. A choice of elements can occur within an element, or may be an unnamed choice of elements.
XML types are represented using the same conventions as for XML elements, though the type portion of the rectangle typically indicates a base type, if any.
The type name of any element, attribute or type may be prefixed with a ↓
, indicating the type is restricted in some fashion by one or more
XML Schema facets (e.g. enumeration). When the type is a union of types, a list of types is presented, each type separated by |
; if the list of union types
is long, the list may be marked with ellipses, e.g., | ...
In an actual XML diagram, element, type and attribute rectangles are usually linked to their corresponding definitions/descriptions in accompanying tables.
The SIF Implementation Specification uses the following version numbering scheme:
major version.
minor version.
revision number(X.Y.Z)
Once a versioned specification (Specification Release) has been released, the contents of that version MUST NOT be modified. Any modifications MUST be released under a new Specification Version Number unless the modification is the correction of an error or update of documentation. Each Specification Release has an associated errata section in which modifications and corrections of the release are listed.
A Specification Version Number for a Specification Release uses conventions as follows:
X.Y.Z
where X
, Y
, and Z
are nonnegative integers (whole numbers), and MUST NOT contain leading zeroes. X
represents the Major version, Y
represents the Minor version, and Z
represents the Revision version.1.9.1
to 1.10
to 1.11
to 1.11.1
.1.0.0
< 2.0.0
< 2.1.0
< 2.1.1
.An instance of a Specification Version Number is the canonical identifier for a Specification Release. The manner in which the Specification Version Number increments after a given Specification Release depends on the type and relative magnitude of changes being proposed in the new release as follows:
1. The Revision version number ( Z
in x.y.Z
, where x
>= 0) MUST be incremented when specification changes are limited to backward compatible changes. If Z
=0 then the convention is to drop the Revision number: for example, 3.1
instead of 3.1.0
. Backward compatible changes include the following:
2. The Minor version number ( Y
in x.Y
.z, where x
> 0 ) MUST be incremented if new functionality is added to the specification. It MUST be incremented if any aspect of the specification is marked as deprecated. It MUST be incremented if any aspect of the specification is not backward compatible. (Backward compatible means any change that can be implemented by one participant (consumer, Environment or service provider) without requiring changes by other participants to maintaining the same level of interoperability.) It MAY be incremented if substantial new functionality or improvements are introduced. It MAY include changes that are categorized as ”Revision” level magnitude. The Revision version MUST be reset to 0 when the Minor version is incremented. Changes requiring a Minor version increment include the following:
3. The Major version number ( X
in X
.y.z, where X
> 0 ) MUST be incremented if a significant change is introduced to the specification. It MAY include changes categorized as Minor and Revision level changes. The Revision and Minor version numbers MUST be reset to 0 when the Major version is incremented. Changes requiring a Major version increment include the following:
This section presents the XML structure for SIF common elements and objects in a tabular format for readers less versed in parsing formal XML schema definitions, along with conventions that typically apply for easy reference.
The Char(acteristics) column for all the tables in this section use the following codes:
Code | Characteristic |
M | Mandatory element or attribute |
O | Optional element or attribute |
C | Conditional element or attribute |
MR | Mandatory and repeatable element |
OR | Optional and repeatable element |
CR | Conditional and repeatable element |
Mandatory elements MUST be present in Add events, and
in non-empty and non-error responses to requests for entire SIF objects (e.g., no SIF_Query/SIF_QueryObject/SIF_Element
elements supplied in the request).
Mandatory attributes MUST always be present if their corresponding element is present.
SIF Adapters and message brokers MUST supply data according to the types specified in the Type columns and their corresponding equivalents in the most recent schema files associated with this specification. If there is a discrepancy between object and element definitions in this specification and the corresponding schema files, the definition in the schema files takes precedence; every effort will be made to note discrepancies in the errata for this document as they are identified.
While XML attributes are primarily used in SIF to provide additional processing information regarding the associated element content, attributes at the root level of an object have special significance. These attributes serve as the primary key or identifier for the object; in all cases this is no more than a id
GUID of uuidType
Note that XML not defined within SIF does not necessarily support ad hoc omission of XML elements at will to conform with the conventions of the SIF Publish/Subscribe Model (where unchanged elements are typically omitted in Change events, and where non-key elements are often omitted in Delete events) or of the SIF Request/Response Model (where a subset of elements can be retrieved from objects with requests). If externally-defined XML occurs within a SIF data object, SIF conventions do not extend to that XML unless that XML is defined to accommodate SIF conventions; the XML, when transmitted, must only conform to any external definitions dictating its structure, if any. Applications should be prepared for the possibility of receiving whole externally-defined XML structures in Change events (regardless of how little or much of the external XML has changed) and possibly also Delete events, likewise in responses even when a subset of the XML structure's child elements may have explicitly been requested.
There are two sets of XSDs available for Validation of Payload.
The first set, called "DataModel" or "Strict" is 'strict' and all of the elements that are required for validation are 'Mandatory' in this suite of XSDs. This suite is traditionally used for Creation of new entities, which generally require validation before being saved into a Data Store.
The second set, called "SIF_Message" or "Lax" is 'lax' and every element within the schema is 'optional' except the 'Id' the identifying GUID/UUID. (However, required elements are not nillable.) This suite of XSDs are traditionally used for Update and Delete of current entities. If an element is not included in the payload of an Update operation, its value is assumed to be unchanged. In addition, if the payload contains the Id/UUID only, the consumer must assume that object to be DELETED or that it has been deleted since the original request was made.
This object contains information about privacy obligations.
SIF_Events are reported for this object.
Figure 3.2.1-1: podElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
pod | Low | This object contains information about privacy obligations. | |||
@![]() | id | M | Low | The ID (GUID) that uniquely identifies this object. | uuidType |
podStatus | M | Low | The status value for this POD. | values:
| |
podToken | M | Low | The token reference for the POD, also conveyed as the dataPrivacyMarker header. | gCoreLocalIdType | |
podVersion | M | Low | The POD version number. PODs are expected to change over time. | xs:normalizedString | |
partyId | M | Low | The name of the party (typically the data processor) which will receive the data from the school, district or state and has entered into an agreement to process the data and respect the privacy obligations of the data. | xs:normalizedString | |
privacyList | M | Low | The set of privacy controls, laws and obligations which apply in this POD. There may be multiple sets which apply. | privacyListType |
A "deleteRequest" element, which consists of multiple, "delete" object ids. Since REST conventions do not support payloads on HTTP DELETE messages, all multi-object Delete Requests are conveyed via an HTTP PUT message containing an additional HTTP Header Field value of methodOverride set to DELETE.
SIF_Events are not reported for this object.
Figure 3.3.1-1: deleteRequestElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
deleteRequest | A "deleteRequest" element, which consists of multiple, "delete" object ids. Since REST conventions do not support payloads on HTTP DELETE messages, all multi-object Delete Requests are conveyed via an HTTP PUT message containing an additional HTTP Header Field value of methodOverride set to DELETE. | ||||
deletes | M | deleteIdCollectionType |
Admin Directives, empowers endpoint providers to “inform” or “direct” endpoint consumers what needs to happen. This opens the possibility to prompt the resending of data, expose what objects have been updated, initiate functional services etc. Some common use-cases and details on Admin Directive functionality can be found on the respective Admin Directives section.
SIF_Events are reported for this object.
Figure 3.4.1-1: adminDirectiveElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
adminDirective | Admin Directives, empowers endpoint providers to “inform” or “direct” endpoint consumers what needs to happen. This opens the possibility to prompt the resending of data, expose what objects have been updated, initiate functional services etc. Some common use-cases and details on Admin Directive functionality can be found on the respective Admin Directives section. | ||||
@![]() | id | O | xs:token | ||
timestamp | M | Timestamp when request was issued. | xs:dateTime | ||
timeout | M | When should the request expire if not fulfilled. | xs:duration | ||
serviceName | M | The name of the Service. For utilities, this is fixed to one of the defined set of Utility Service Names. For objects and functions, it is defined by the Data Model. | xs:token | ||
method | M | Unique ID/Name or requested method. | xs:token | ||
methodParameters | O | methodParametersType |
An HTTP Response with a status of 200 and a payload consisting of a single "createResponse" element. This includes, for each requested object successfully created, an internal status of 201 and the service-assigned refId. Any requested object that failed to be created is indicated by an error statusCode and a corresponding error payload.
SIF_Events are not reported for this object.
Figure 3.4.2-1: createResponseElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
createResponse | An HTTP Response with a status of 200 and a payload consisting of a single "createResponse" element. This includes, for each requested object successfully created, an internal status of 201 and the service-assigned refId. Any requested object that failed to be created is indicated by an error statusCode and a corresponding error payload. | ||||
creates | M | createsType |
An HTTP Response with a status of 200 (success). It contains a payload consisting of a single "deleteResponse" element.
SIF_Events are not reported for this object.
Figure 3.4.3-1: deleteResponseElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
deleteResponse | An HTTP Response with a status of 200 (success). It contains a payload consisting of a single "deleteResponse" element. | ||||
deletes | M | deleteStatusCollectionType |
SIF_Events are reported for this object.
Figure 3.4.4-1: errorElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
error | Extension of errorCommonType | ||||
@ | id | O | xs:token | ||
code | M | Corresponds to the value contained in the HTTPS Header Status-Code" field in which the Error Object is the payload. | xs:unsignedInt | ||
scope | M | Attempted operation. Ex: "Modify Student" | xs:string | ||
type | O | Indicator if the error relates to infrastructure or data. | errorTypeType values:
| ||
subCode | O | Machine readable second code used to eliminate ambiguity. | xs:string | ||
message | M | A simple, easy to understand, compact description of the error. The primary consumer of this message is the application user. Example: "Unable to open database." | xs:string | ||
description | O | An optional error description that is more complete and technical in nature. It is to be used as a diagnostic message in trouble-shooting procedures. Example: "The 'Students' table is opened in exclusive mode by user 'ADM1' (dbm.cpp, line 300)." | xs:string | ||
errorDetails | O | errorDetailsType |
An HTTP Response with a status of 200 (success) and a location corresponding to the URL of the first successfully modified object. It contains a payload consisting of a single "updateResponse" element.
SIF_Events are not reported for this object.
Figure 3.4.5-1: updateResponseElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
updateResponse | An HTTP Response with a status of 200 (success) and a location corresponding to the URL of the first successfully modified object. It contains a payload consisting of a single "updateResponse" element. | ||||
updates | M | updatesType |
The Consumer Environment Service is the gateway to all other services. It scopes the Consumer's possible interactions with the infrastructure and any Provider Services accessible from it. The Environment Service provides the set of (possibly customized) information the Application needs to interoperate successfully.
SIF_Events are not reported for this object.
Figure 3.5.1-1: environmentElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
environment | The Consumer Environment Service is the gateway to all other services. It scopes the Consumer's possible interactions with the infrastructure and any Provider Services accessible from it. The Environment Service provides the set of (possibly customized) information the Application needs to interoperate successfully. | ||||
@ | type | O | environmentTypeType values:
| ||
@![]() | id | O | uuidType | ||
fingerprint | O | Unique environment identifier that can be safely shared with others. In order to not compromise security it MUST NOT match the environment's refId, sessionToken, userToken, or applicationKey. | xs:token | ||
sessionToken | O | xs:token | |||
solutionId | O | The solution the Application would like to participate in. This is optional only, is advisory, and may be ignored by the Administrator. If processed it may be reflected in the URLs of the infrastructure services which are provided in the consumerEnvironment. | xs:token | ||
defaultZone | O | defaultZoneType | |||
authenticationMethod | O | Defines the way in which the applicationKey can be used to enforce security. | xs:token | ||
instanceId | O | xs:token | |||
userToken | O | xs:string | |||
consumerName | O | A descriptive name for the application that will be readily identifiable to Zone Administrators if it becomes a Registered Consumer | xs:string | ||
applicationInfo | O | applicationInfoType | |||
infrastructureServices | O | infrastructureServicesType | |||
provisionedZones | O | provisionedZonesType |
All functional services must use this object design to track state. While Events may be published back to the objects creator, they must not be published to the Consumer when the event was generated based on its request (since results were included in the response). Each functional service should define the expectations of how management of the job is managed for both the Consumer and Provider. For instance, certain optional fields may need to be included in-order-to successfully cause a job to be created.
SIF_Events are reported for this object.
Figure 3.5.2-1: jobElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
job | All functional services must use this object design to track state. While Events may be published back to the objects creator, they must not be published to the Consumer when the event was generated based on its request (since results were included in the response). Each functional service should define the expectations of how management of the job is managed for both the Consumer and Provider. For instance, certain optional fields may need to be included in-order-to successfully cause a job to be created. | ||||
@![]() | id | O | uuidType | ||
name | M | The name of the job, e.g. "grading" or "sre". | xs:token | ||
description | O | A description of the job, e.g. "Bowers Elementary School Final Marks" | xs:string | ||
state | O | The current enumerable state of the job. | jobStateType values:
| ||
stateDescription | O | A descriptive message elaborating on the current state, e.g. if the current state is "FAILED" the stateDescription may be "Timeout occured". | xs:string | ||
created | O | The datetime this job was created. | xs:dateTime | ||
lastModified | O | The datetime this job was last modified. | xs:dateTime | ||
timeout | O | The ammount of time after creation before this job is automatically deleted. | xs:duration | ||
phases | O | The phases that make up this job. | phaseCollectionType | ||
initialization | O | initializationType |
If an Environment supports self-provisioning Consumers than either this section must initially contain all the rights the Consumer has to all Services in all Zones, or the provisionRequests Infrastructure Service must be present in the Consumer's Environment to allow additional rights to be obtained.
SIF_Events are not reported for this object.
Figure 3.5.3-1: provisionRequestElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
provisionRequest | If an Environment supports self-provisioning Consumers than either this section must initially contain all the rights the Consumer has to all Services in all Zones, or the provisionRequests Infrastructure Service must be present in the Consumer's Environment to allow additional rights to be obtained. | ||||
@![]() | id | O | Low | uuidType | |
@ | completionStatus | O | values:
| ||
provisionedZones | M | A specific Zone defined for this environment. | provisionedZonesType |
The Queues Service supports creation, deletion and querying of Queue (Instance) / Queue Messages Service pairs.
SIF_Events are not reported for this object.
Figure 3.5.4-1: queueElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
queue | The Queues Service supports creation, deletion and querying of Queue (Instance) / Queue Messages Service pairs. | ||||
@![]() | id | O | uuidType | ||
polling | O | Determines, when no messages are queued, whether the Consumer will have to periodically reissue Polling Requests at timed intervals or can reissue a Polling Request immediately. | values:
| ||
ownerId | C | The Environment ID of the owning Consumer for which this Queue is buffering messages. It is not specified at Queue create time, but is returned as part of the response to a query operation, and serves to allow an administrative application to identify which application the Queue instance is assigned to. | uuidType | ||
name | O | A name which the Consumer assigns to the Queue. It is useful for reporting purposes, but is not guaranteed to be unique. | xs:token | ||
queueUri | O | The URI of the Messages Service associated with the Queue instance. This is the endpoint where the 'get next message' requests are issued. | xs:anyURI | ||
ownerUri | O | When present, this contains the URL which the Queue instance will use when it determines the owner needs to be asynchronously alerted that a new message has arrived in the Queue. | xs:anyURI | ||
idleTimeout | O | Is the maximum time in seconds the Messages Service will wait for a message to arrive, before returning an HTTPS Response of 'no message seen' to the Consumer. | xs:unsignedInt | ||
minWaitTime | C | indicates the minimum time in seconds that the Consumer should wait after receiving a 'no message seen' response to a previous query, before posting another. | xs:unsignedInt | ||
maxConcurrentConnections | O | Number of (properly identified) concurrent connections supported by (the consumer, if suggested, and) the queue. | xs:unsignedInt | ||
created | O | Time that Queue Instance was Created | xs:dateTime | ||
lastAccessed | O | Time that Queue Instance was last Accessed and a message was dequeued. | xs:dateTime | ||
lastModified | O | Time that Queue Instance was last Modified by receiving a new incoming message. | xs:dateTime | ||
messageCount | O | The number of messages currently residing in the Queue. | xs:unsignedInt |
For states updatable by the Consumer, it creates a new state much like it would a single object. The actual result (state or error) is included in the response. Each functional service should define the expectations for which Adaptor is responsible for updating the phase status. NOTE: The "states" collection represented here is reserved for future capabilities.
SIF_Events are reported for this object.
Figure 3.5.5-1: stateElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
state | For states updatable by the Consumer, it creates a new state much like it would a single object. The actual result (state or error) is included in the response. Each functional service should define the expectations for which Adaptor is responsible for updating the phase status. NOTE: The "states" collection represented here is reserved for future capabilities. | Extension of stateCommonType | |||
@ | id | O | uuidType | ||
type | M | The type of this State object. | phaseStateType values:
| ||
created | O | The datetime this job was created. | xs:dateTime | ||
lastModified | O | The datetime this job was last modified. | xs:dateTime | ||
description | O | A descriptive message ellaborating the condition of this state, e.g. if the state is "FAILED" the stateDescription may be "Timeout occured". | xs:string |
A Consumer uses the Subscriptions Infrastructure Service to subscribe to Events published by one or more Service Providers.
SIF_Events are not reported for this object.
Figure 3.5.6-1: subscriptionElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
subscription | A Consumer uses the Subscriptions Infrastructure Service to subscribe to Events published by one or more Service Providers. | ||||
@![]() | id | O | uuidType | ||
zoneId | M | xs:token | |||
contextId | O | The unique identity of a context element, which is associated with a Provider of this name and type operating in a Zone with this ID. | xs:token | ||
serviceType | M | The type of the service | serviceTypeType values:
| ||
serviceSubType | O | The subtype of the Service | serviceSubTypeType values:
| ||
messageType | O | The type of the message | messageTypeType values:
| ||
serviceName | M | The name of the Service. For utilities, this is fixed to one of the defined set of Utility Service Names. For objects and functions, it is defined by the Data Model. | xs:token | ||
queueId | M | Specifies which queues you want data associated with this subscription published to. | xs:token |
Alerts form a system wide log that can be protected, as it may contain sensitive data. Ideally an Alert should contain as much identifying information about the problem being reported as possible.
SIF_Events are not reported for this object.
Figure 3.6.1-1: alertElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
alert | Alerts form a system wide log that can be protected, as it may contain sensitive data. Ideally an Alert should contain as much identifying information about the problem being reported as possible. | ||||
@![]() | id | O | uuidType | ||
reporter | M | External identification of the Application (Consumer or Provider) reporting this Alert. | xs:token | ||
cause | O | External identification of the cause of the Alert. | xs:token | ||
exchange | M | The exchange (or lack of exchange) responsible for generating the Alert. | values:
| ||
level | M | The level of the Alert. | values:
| ||
description | O | A description of the reason for the Alert. | xs:normalizedString | ||
messageID | C | If available, the ID of the Message causing the problem. | xs:token | ||
body | O | The internals of the offending message or a more complete description of the information or state change. Usage of the CDATA designation is recommended in order to make the XML contents more readable to humans. | xs:string | ||
error | O | Detailed error results such as a stack trace. | xs:string | ||
xpath | O | An indicator of the specific element that was in error (or contributed to the problem. [NEEDS TO BE CHANGED TO the SIF XPATH TYPE] | xs:normalizedString | ||
category | C | If the Alert Level is an error, this value must be the SIF 3.0.1 Error Category corresponding to the type of Error being reported | xs:unsignedInt | ||
code | C | If the Alert Level is an error, this value must be the SIF 3.0.1 Error Code corresponding to the type of Error being reported. | xs:unsignedInt | ||
internal | O | Code internal to the reporter. | xs:token |
The Code Set Registry Service provides a way for all legal codes to be defined outside of the SIF Specification while allowing changes (additions and replacements) of external code set values to be easily verified by the recipient so as not to break existing Consumer / Provider interoperability.
SIF_Events are not reported for this object.
Figure 3.6.2-1: codeSetElement/@Attribute | Char | Privacy Rating | Description | Type | |||||
---|---|---|---|---|---|---|---|---|---|
codeSet | The Code Set Registry Service provides a way for all legal codes to be defined outside of the SIF Specification while allowing changes (additions and replacements) of external code set values to be easily verified by the recipient so as not to break existing Consumer / Provider interoperability. | ||||||||
@![]() | id | O | xs:token
| ||||||
zone | M | If this is tied to a specific zone it is specified here, otherwise "environment-global" indicates applicability to all zones in the Environment. | xs:token | ||||||
version | M | The official major, minor, and revision version of the code set. | versionType | ||||||
timestamp | M | The date and time of the last change to this code set. So that only updates can be queried efficiently (where applicable). | xs:dateTime | ||||||
source | C | URL to an external code set whose values are not (yet) present in the system. | uriType | ||||||
codeItems | O | codeItemsType |
The Namespaces Registry contains the set of XML namespace URIs and their corresponding schema location URLs that are currently valid within the Environment.
SIF_Events are reported for this object.
Figure 3.6.3-1: namespaceElement/@Attribute | Char | Privacy Rating | Description | Type | |||
---|---|---|---|---|---|---|---|
namespace | The Namespaces Registry contains the set of XML namespace URIs and their corresponding schema location URLs that are currently valid within the Environment. | ||||||
@![]() | id | O | uuidType | ||||
zone | M | If this namespace is tied to a specific zone it is specified here. | xs:token | ||||
uri | M | The namespace URI of the retrieved URL. | xs:anyURI
| ||||
url | M | The URL of the specified namespace URI. | xs:anyURI
|
All potentially accessible Services have an entry in the Providers Registry (including the Providers Registry Utility Service itself), although full or even partial Consumer access to that Service is determined by the access rights currently granted in the Consumer's Environment object, and is not guaranteed.
SIF_Events are reported for this object.
Figure 3.6.4-1: providerElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
provider | All potentially accessible Services have an entry in the Providers Registry (including the Providers Registry Utility Service itself), although full or even partial Consumer access to that Service is determined by the access rights currently granted in the Consumer's Environment object, and is not guaranteed. | ||||
@![]() | id | O | uuidType | ||
serviceType | M | The generic type of Service being provided. | serviceTypeType values:
| ||
serviceName | M | The name of the Service or the Service Path being provided. | xs:token | ||
contextId | M | The name of the Service Context being provided. | xs:token | ||
zoneId | M | The Zone in which the Service Context is being provided. | xs:token | ||
providerName | M | The name of the Service Provider as it would be referred to by the administrator of the Zone (ex: RamseySIS). | xs:token | ||
querySupport | M | querySupportType | |||
mimeTypes | O | mediaTypesType | |||
endPoint | C | In a Brokered Environment, this element contains the URL where all requests for this Service Provider should be re-invoked by the Connector | protocolType | ||
supportedRequestTypes | O | supportedRequestsType |
This collection defines the entire set of named queries that Consumers may legally issue for execution by Service Providers. A Consumer specifies the ID of a Named XQuery in a Query Request to a specific Service Provider, along with a set of values for any associated script parameters.
SIF_Events are reported for this object.
Figure 3.6.5-1: xqueryElement/@Attribute | Char | Privacy Rating | Description | Type | |||||
---|---|---|---|---|---|---|---|---|---|
xquery | This collection defines the entire set of named queries that Consumers may legally issue for execution by Service Providers. A Consumer specifies the ID of a Named XQuery in a Query Request to a specific Service Provider, along with a set of values for any associated script parameters. | ||||||||
@![]() | id | C | The unique ID of the XQuery Template, which is contained in the Query Request URL when this template is being utilized. "Suggested" by the Consumer issuing the create Request, or pre-set in accordance with the binding requirements of a particular SIF release. This is NOT required to be a UUID, and must be provided as the Service Identifier in every Query URL which invokes this Template. Ex: "StudentSnapshot". | xs:token | |||||
type | M | Determines if the query may be sent to a data provider or if it requires the extended XQuery mechanism. | values:
| ||||||
status | M | Communicates if the query has been inspected for data hiding and the results of that assessment. | values:
| ||||||
qualifier | O | If status is DISALLOWED this element optionally contains the reason. | xs:string
| ||||||
description | O | Human readable description of the XQuery's intended behavior. | xs:string
| ||||||
script | M | The text of the XQuery which MAY accept parameters. Usage of the CDATA designation is recommended. An empty value indicates the query is implimented wihtout XQuery or its logic is not disclosed | xs:string
| ||||||
parameters | M | parametersType | |||||||
returnType | M | The fully qualified name of the root element returned by this service. Example: http://www.sifassociation.org/datamodel/na/3.3:students | xs:anyURI |
Zone identifiers are chosen by the administrator and can follow any convention that best meets the needs of the deploying organization. The Zone in which the Service is to be found always qualifies every Consumer request for any Provider Service. Each Service Consumer is assigned a "default" Zone at Registration time, which is used whenever a specific Zone is not explicitly included in one of its Provider Service Requests.
SIF_Events are not reported for this object.
Figure 3.6.6-1: zoneElement/@Attribute | Char | Privacy Rating | Description | Type | |
---|---|---|---|---|---|
zone | Zone identifiers are chosen by the administrator and can follow any convention that best meets the needs of the deploying organization. The Zone in which the Service is to be found always qualifies every Consumer request for any Provider Service. Each Service Consumer is assigned a "default" Zone at Registration time, which is used whenever a specific Zone is not explicitly included in one of its Provider Service Requests. | ||||
@![]() | id | O | xs:token | ||
description | O | A short (possibly multi-sentence) description of the Zone | xs:normalizedString | ||
properties | O | propertiesType |
Common and supporting types referenced in this specification are included here as a reference.
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
adapterFingerprintListType | List | |||
adapterFingerprint | OR | An opaque marker that represents the amalgam of all underlying PODs tied to a specific DataProcessor-DataController relationship. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
aliasesType | List | |||
alias | MR | aliasType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
aliasType | ||||
code | M | codeType | ||
source | O | URL where the related abbreviation comes from. | uriType | |
namespace | O | Namespace where the related abbreviation comes from. | uriType |
Purposes for which the data may be shared beyond its orginal uses.
Figure A.4-1: alternatePurposeListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
alternatePurposeListType | Purposes for which the data may be shared beyond its orginal uses. | List | ||
alternatePurpose | OR | A purpose for which the data may be shared beyond its orginal uses. | xs:normalizedString |
List of application identifiers.
Figure A.5-1: appIDListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
appIDListType | List of application identifiers. | List | ||
appID | OR | The name of the software providing the services for a particular data source. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
applicationInfoType | ||||
applicationKey | O | An opaque (to the SIF standard) element which contains any required Consumer authentication information. The content of this element is site-specific. For a Direct Environment which accepts Consumer Registration Requests from a mobile application, this element might contain a combination of the User ID and Password. | xs:string | |
supportedInfrastructureVersion | O | The version of the SIF infrastructure which the Consumer supports. | xs:string | |
dataModelNamespace | O | The namespace of the data payloads conveyed by this environment. Returns may be of a diffrent minor version. Utility payloads will be of the infrastructure namespace. | xs:anyURI | |
transport | O | The transport which the Consumer expects the infrastructure to use to interoperate with it. The default is whichever transport the create request was issued on | xs:string | |
applicationProduct | O | productIdentityType | ||
adapterProduct | O | productIdentityType |
A List of benchmarks - where a benchmark is a set of technical or process standards to ensure the clause is met.
Figure A.7-1: benchmarkListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
benchmarkListType | A List of benchmarks - where a benchmark is a set of technical or process standards to ensure the clause is met. | List | ||
benchmark | OR | A benchmark is a set of technical or process standards to ensure the clause is met. | benchmarkType |
A set of technical or process standards to ensure the clause is met.
Figure A.8-1: benchmarkTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
benchmarkType | A set of technical or process standards to ensure the clause is met. | |||
benchmarkName | O | A name given to the evidence against which privacy obligations or requirements may be assessed or measured. | xs:normalizedString | |
benchmarkId | O | A unique identifier assigned to an instance of the evidence against which privacy obligations or requirements may be assessed or measured. | gCoreLocalIdType | |
benchmarkDescription | O | A description of the evidence against which privacy obligations or requirements may be assessed or measured. | xs:normalizedString | |
benchmarkURL | O | A URL pointing to the evidence against which privacy obligations or requirements may be assessed or measured. | xs:anyURI |
A list of the legal clauses within the contract.
Figure A.9-1: clauseListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
clauseListType | A list of the legal clauses within the contract. | List | ||
clause | OR | Details of a legal clause within the contract. | clauseType |
Details of a legal clause within the contract.
Figure A.10-1: clauseTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
clauseType | Details of a legal clause within the contract. | |||
clauseLabel | O | A human friendly handle for refering to the associated clause. | xs:normalizedString | |
clauseReference | O | An exact reference within the contract to a specific clause. | xs:normalizedString | |
clauseContent | O | The actual detailed content of the clause. | xs:normalizedString | |
obligationList | O | List of obligations. | obligationListType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
codeItemsType | List | |||
codeItem | MR | codeItemType |
Element/@Attribute | Char | Description | Type | |||||
---|---|---|---|---|---|---|---|---|
codeItemType | ||||||||
code | M | Official abbreviation for the given value. | xs:string | |||||
source | O | URL where the related abbreviation comes from. | uriType | |||||
namespace | O | Namespace where the related abbreviation comes from. | uriType | |||||
value | M | What the code represents. | xs:token
| |||||
description | O | Human readable explanation of what the code represents. | xs:normalizedString
| |||||
definition | O | Human readable explanation provided by the source! | xs:normalizedString
| |||||
aliases | O | aliasesType | ||||||
action | M | The last action to be taken for this code item. | values:
| |||||
timestamp | M | The date and time of the last action taken on this code item. So that only updates can be queried efficiently (where applicable). | xs:dateTime |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
codeType | ||||
old | M | Indicates the alias code has been deprecated or deleted, even if it no longer appears in the register. | xs:boolean | |
official | M | Indicates the alias code is an official one; however the locale uses this one to represent that concept, at least in part. | xs:boolean | |
value | M | Alternate abbreviation that might need to be more specific or correct. | xs:string |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
conditionListType | List | |||
condition | OR | conditionType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
conditionType | ||||
typeOfCondition | O | The name of the parameter used fo enforce the privacy condition. | xs:normalizedString | |
conditionName | O | The name of the parameter used to enforce the privacy condition. | xs:normalizedString | |
conditionDescription | O | The explanation of what the related privacy conditions combine to do in plain terms. | xs:normalizedString | |
propertyList | O | propertyNVListType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
contractType | O | The details of the contract the POD has been derived from. | ||
contractURI | M | URI associated with contract. This may be a resolvable URL or just a unique identifier. | xs:anyURI | |
contractName | M | Name associated with contract | xs:normalizedString | |
dateValidFrom | M | The initial date that the contract is enforceable. | xs:date | |
dateValidTo | O | The date the contract expires and is no longer enforcable. | xs:date | |
contractVersion | O | The version of the contract being represented by the associated elements. | xs:normalizedString | |
lawList | M | List of laws covered referenced by the contract. | lawListType | |
studentDataIPRights | O | Who owns the intellectual property for any student under this contract. | xs:normalizedString |
List of impacted countries in or through which the data transits or is stored.
Figure A.17-1: countryImpactedListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
countryImpactedListType | List of impacted countries in or through which the data transits or is stored. | List | ||
countryImpacted | OR | Name of a country impacted in or through which the data transits or is stored. | countryImpactedType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
countryImpactedType | ||||
country | O | Name of a country impacted in or through which the data transits or is stored. | gCoreCountryType | |
usage | O | Country specific details about how the processor handles the data. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
createsType | List | |||
create | MR | createType |
Element/@Attribute | Char | Description | Type | |||
---|---|---|---|---|---|---|
createType | ||||||
@ | id | O | xs:token | |||
@ | advisoryId | M | xs:token | |||
@ | statusCode | O | xs:token
| |||
error | O | errorCommonType |
A list of the data that can be accessed and any rules that specifically apply.
Figure A.21-1: dataAccessTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
dataAccessType | A list of the data that can be accessed and any rules that specifically apply. | |||
clauseList | O | A list of clauses that specifically apply to these technical requirements. | clauseListType | |
fieldList | O | A list of fields that can be accessed under this POD. Equivalent to a green list. | fieldListType |
The data controller, means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data, see GDPR.
Figure A.22-1: dataControllerTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
dataControllerType | The data controller, means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data, see GDPR. | |||
dataControllerName | O | The name of the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data. | xs:normalizedString | |
privacyPolicyURL | M | URL Associated with contract | xs:anyURI | |
privacyContactList | O | The details of the privacy contact. | gCoreContactListType | |
issuesNotificationContactList | O | The details of the individual to be contacted if there are issues in fulfilling the obligations of the contract. | gCoreContactListType |
Details and requirements for data deletion.
Figure A.23-1: dataDeletionTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
dataDeletionType | Details and requirements for data deletion. | |||
deleteData | O | Flag indicating that the data must be deleted when no longer requred for the primary purpose. | values:
| |
dataRetention | O | If allowed, the length of time the data be retained when no longer required for the primary purpose. | xs:integer | |
deleteBy | O | The specific date should this data be removed from the systems. | xs:date | |
partyToDeleteData | O | Who is responsible for deletion of this data? | partyToDeleteDataType | |
respondInDays | O | Maximum response time, number of days, for information regarding this data. | xs:integer | |
requirePortability | O | Flag indicating that the rules surrounding this data must be ported with applicable data that is transmitted. | values:
|
The data processor, means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller, see GDPR.
Figure A.24-1: dataProcessorTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
dataProcessorType | The data processor, means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller, see GDPR. | |||
dataProcessorName | O | The label for the vendor who will be accessing, consuming and/or providing information back to the controller. | xs:normalizedString | |
privacyPolicyURL | M | URL Associated with contract | xs:anyURI | |
privacyContactList | O | The details of the privacy contact. | gCoreContactListType | |
notifyDataControllerOnAccessRequests | O | Indicates if the processor needs to advise the controller of access requests. | values:
| |
dataProcessorContactForAccessRequestsList | O | The details of the person to contact for access requests. | gCoreContactListType | |
purposeList | O | A list or purposes for which the data may be used. | purposeListType | |
alternatePurposeList | O | A purpose for which the data may be shared beyond its orginal uses. | alternatePurposeListType | |
deidentifiedPurposeList | O | The purposes for which deidentified data is able to be used (if any). | deidentifiedPurposeListType | |
dataUsageMarketingAllowed | O | Determines whether the data may be used for marketing purposes. | values:
| |
personalInformationUpdatedFromSource | O | The frequency at which personal information is to be updated from source systems, including deletions. | xs:integer | |
dataBreachNotification | O | Determines if notification of those in the breach contact list is required. | values:
| |
dataBreachContactList | O | Contact details for the individual/s to be notified in the event of a data breach. | gCoreContactListType | |
employeesMustComplyWithAgreement | O | Determines whether the data controller and their staff must also comply with the privacy agreement. | values:
| |
employeeConfidentialityAgreement | O | Determines whether the data controller and their staff must also comply with the confidentiality agreement. | values:
| |
employeeTrainingList | O | A list of the data controller employee’s training requirements. | employeeTrainingListType | |
passwordEmployeeAccessStandard | O | A list of the data controller employee’s password access standards. | passwordEmployeeAccessStandardType | |
securityTestRequiredList | O | A list of security testing required to be completed by the data controller. | securityTestRequiredListType | |
countryImpactedList | O | List of impacted countries in or through which the data transits or is stored. | countryImpactedListType |
The specific clauses obligations and benchmarks that applies to the subject - teacher, student or parent.
Figure A.25-1: dataSubjectTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
dataSubjectType | The specific clauses obligations and benchmarks that applies to the subject - teacher, student or parent. | |||
clauseList | O | clauseListType | ||
benchmarkList | O | benchmarkListType | ||
fieldList | O | A list of fields that can be accessed under this POD. Equivalent to a green list. | fieldListType | |
respondInDays | O | Maximum response time, number of days, for information regarding this data. | xs:integer | |
requirePortability | O | Flag indicating that the rules surrounding this data must be ported with applicable data that is transmitted. | values:
|
The list of data sub-Processors who are the bodies that process data on behalf of the Data Processor.
Figure A.26-1: dataSubProcessorListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
dataSubProcessorListType | The list of data sub-Processors who are the bodies that process data on behalf of the Data Processor. | List | ||
dataSubProcessor | OR | A data sub-Processors who are the bodies that process data on behalf of the Data Processor. | dataSubProcessorType |
Details of organisations who process data on behalf of the data processor.
Figure A.27-1: dataSubProcessorTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
dataSubProcessorType | Details of organisations who process data on behalf of the data processor. | |||
subProcessorName | O | The name of the natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller. | xs:normalizedString | |
privacyPolicyURL | M | URL Associated with contract | xs:anyURI | |
privacyContactList | O | Details of the data sub processor`s privacy contact. | gCoreContactListType | |
purposeList | O | The purpose for which data is supplied to the data sub processor by the data processor. | purposeListType |
Zone identifiers are chosen by the administrator and can follow any convention that best meets the needs of the deploying organization. The Zone in which the Service is to be found always qualifies every Consumer request for any Provider Service. Each Service Consumer is assigned a "default" Zone at Registration time, which is used whenever a specific Zone is not explicitly included in one of its Provider Service Requests.
Figure A.28-1: defaultZoneTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
defaultZoneType | Zone identifiers are chosen by the administrator and can follow any convention that best meets the needs of the deploying organization. The Zone in which the Service is to be found always qualifies every Consumer request for any Provider Service. Each Service Consumer is assigned a "default" Zone at Registration time, which is used whenever a specific Zone is not explicitly included in one of its Provider Service Requests. | |||
@ | id | O | xs:token | |
description | O | A short (possibly multi-sentence) description of the Zone | xs:normalizedString | |
properties | O | propertiesType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
DefinedProtocolsType | The transport protocols defined in SIF. | values:
|
A purposes for which deidentified data may be used.
Figure A.30-1: deidentifiedPurposeListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
deidentifiedPurposeListType | A purposes for which deidentified data may be used. | List | ||
deidentifiedPurpose | OR | A purpose for which deidentified data may be used. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
deleteIdCollectionType | List | |||
delete | MR | deleteIdType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
deleteIdType | EMPTY | |||
@ | id | M | xs:token |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
deleteStatusCollectionType | List | |||
delete | MR | deleteStatusType |
Element/@Attribute | Char | Description | Type | |||
---|---|---|---|---|---|---|
deleteStatusType | ||||||
@ | id | O | xs:token | |||
@ | statusCode | O | xs:token
| |||
error | O | errorCommonType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
employeeTrainingListType | List | |||
employeeTraining | OR | employeeTrainingType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
employeeTrainingType | ||||
trainingName | O | The label of the training being given to employees to teach privacy requirements and practices. | xs:normalizedString | |
trainingURL | O | The URL of the training being given to employees to teach privacy requirements and practices. | xs:anyURI |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
endpointListType | List | |||
endpoint | OR | An endpoint covered by the POD. | endpointType |
A type of endpoint.
Figure A.38-1: endpointTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
endpointType | A type of endpoint. | |||
endpointURL | O | The url of the endpoint. | xs:anyURI | |
endpointProviderName | O | The name of the provider of the endpoint. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
enumerationsType | List | |||
enumeration | MR | Individual setting | enumerationType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
enumerationType | ||||
value | M | An acceptable parameter value for this query. | xs:token | |
code | C | If enumerated value has an equivalent code, this field may be used for conversion. | xs:token |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
environmentTypeType | O | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
errorCommonType | ||||
@ | id | O | xs:token | |
code | M | Corresponds to the value contained in the HTTPS Header Status-Code" field in which the Error Object is the payload. | xs:unsignedInt | |
scope | M | Attempted operation. Ex: "Modify Student" | xs:string | |
type | O | Indicator if the error relates to infrastructure or data. | errorTypeType values:
| |
subCode | O | Machine readable second code used to eliminate ambiguity. | xs:string | |
message | M | A simple, easy to understand, compact description of the error. The primary consumer of this message is the application user. Example: "Unable to open database." | xs:string | |
description | O | An optional error description that is more complete and technical in nature. It is to be used as a diagnostic message in trouble-shooting procedures. Example: "The 'Students' table is opened in exclusive mode by user 'ADM1' (dbm.cpp, line 300)." | xs:string | |
errorDetails | O | errorDetailsType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
errorDetailsType | List | |||
errorDetail | OR | errorDetailType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
errorDetailType | ||||
@ | id | O | xs:token | |
type | O | Indicator if the error relates to infrastructure or data. | errorTypeType values:
| |
subCode | O | Machine readable second code used to eliminate ambiguity. | xs:string | |
message | M | A simple, easy to understand, compact description of the error. The primary consumer of this message is the application user. Example: "Unable to open database." | xs:string | |
description | O | An optional error description that is more complete and technical in nature. It is to be used as a diagnostic message in trouble-shooting procedures. Example: "The 'Students' table is opened in exclusive mode by user 'ADM1' (dbm.cpp, line 300)." | xs:string |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
errorTypeType | O | values:
|
A list of fields that can be accessed under this POD. Equivalent to a green list.
Figure A.47-1: fieldListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
fieldListType | A list of fields that can be accessed under this POD. Equivalent to a green list. | List | ||
field | OR | Details of a field that can be accessed under this POD, equivalent to an element in a green list. | fieldType |
Details of a field that can be accessed under this POD, equivalent to an element in a green list.
Figure A.48-1: fieldTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
fieldType | Details of a field that can be accessed under this POD, equivalent to an element in a green list. | |||
fieldName | O | The full unique path for the data field being granted access to. | xs:normalizedString | |
controlrights | O | The level of access being granted to the data. | values:
|
A list of Address elements.
Figure A.49-1: gCoreAddressListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreAddressListType | A list of Address elements. | List | ||
address | MR | Extension of gCoreAddressType |
This element contains address data
Figure A.50-1: gCoreAddressTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreAddressType | M | This element contains address data. | ||
effectiveFromDate | O | Date the address became valid. | xs:date | |
effectiveToDate | O | Date the address ceases to be valid. | xs:date | |
line1 | M | Address line 1. | xs:normalizedString | |
line2 | O | Address line 2. | xs:normalizedString | |
line3 | O | Address line 3. | xs:normalizedString | |
city | M | The city or Suburb part of the address. | xs:normalizedString | |
stateProvince | C | The state or province or county. | gCoreStateProvinceType | |
country | O | The country code. | gCoreCountryType | |
postalCode | M | The ZIP/postal code. | xs:normalizedString |
Common element used to supply information for a contact person at a school, LEA, or other institution.
Figure A.51-1: gCoreContactInfoTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreContactInfoType | Common element used to supply information for a contact person at a school, LEA, or other institution. | |||
name | M | gCoreNameType | ||
positionTitle | O | The contact person`s position title. Examples | xs:normalizedString | |
role | O | Role played by this contact in this instance. Examples | xs:normalizedString | |
registrationDetails | O | Registration Details of the Contact. | xs:normalizedString | |
qualifications | O | Qualifications of the Contact. | xs:normalizedString | |
address | O | Address of the contact. | gCoreAddressType | |
emailList | O | List of Email elements. | gCoreEmailListType | |
phoneNumberList | O | List of PhoneNumber elements. | gCorePhoneNumberListType |
List of Contacts associated with an entity.
Figure A.52-1: gCoreContactListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreContactListType | List of Contacts associated with an entity. | List | ||
contact | MR | gCoreContactInfoType |
A country code or name.
Figure A.53-1: gCoreCountryTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreCountryType | A country code or name. | xs:normalizedString |
A list of e-mail addresses associated with an individual or organization.
Figure A.54-1: gCoreEmailListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreEmailListType | A list of e-mail addresses associated with an individual or organization. | List | ||
MR | The email address. | gCoreEmailType |
This element represents an e-mail address of one of a number of types and occurs in objects such as StudentPersonal, StaffPersonal, StudentContactPersonal, etc..
Figure A.55-1: gCoreEmailTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreEmailType | M | This element represents an e-mail address of one of a number of types and occurs in objects such as StudentPersonal, StaffPersonal, StudentContactPersonal, etc.. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreGenderType | values:
|
This is a common element used to define the locally assigned identifier associated with an entity.
Figure A.57-1: gCoreLocalIdTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreLocalIdType | This is a common element used to define the locally assigned identifier associated with an entity. | xs:normalizedString |
Core Name Type or Name
elements, primarily to allow structure to be leveraged with different Type
attribute values.
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreNameType |
Core Name Type or | |||
title | O | A title or prefix associated with the name. If any of: Mr, Mrs, Ms, Miss, Rev, Fr, Dr, Prof, Hon, Sir, Lord, Lady - these must be as shown, otherwise free text. Note that title is not applicable to learners. | xs:normalizedString | |
familyName | C | Family name. That part of the person`s name which is used to describe family, clan, tribal group, or marital association. Note that this element is required when known. However, it may not be possible to know the family name in which case you should add the available information to the FullName element. | xs:normalizedString | |
givenName | C | Given name of the person. Note that this element is required if known. However, it may not be possible to know the given name in which case you should add the available information to the FullName element. | xs:normalizedString | |
otherGivenNames | O | All other given or middle names, each separated with a single space character. | xs:normalizedString | |
familyNameFirst | O | An indicator used to identify the naming conventions used by some predominantly non-European, ethnic or language groups and related to the display nature of a name. | values:
| |
preferredName | O | The given name preferred most by the person (as written). | xs:normalizedString |
Lists phone numbers associated with an entity.
Figure A.59-1: gCorePhoneNumberListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCorePhoneNumberListType | Lists phone numbers associated with an entity. | List | ||
phoneNumber | MR | gCorePhoneNumberType |
This element represents a phone number and occurs within objects such as StudentPersonal, StaffPersonal, etc.
Figure A.60-1: gCorePhoneNumberTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCorePhoneNumberType | This element represents a phone number and occurs within objects such as StudentPersonal, StaffPersonal, etc. | |||
number | M | Phone number. Free-form, but typical Australian formats include:
| xs:normalizedString | |
extension | O | Phone number extension. | xs:normalizedString | |
listedStatus | O | Indicates whether or not the phone number is available to the public. | values:
| |
preference | O | Preference number indicating an order in which phone numbers should be used when contacting person. | xs:unsignedInt |
The identifier for this entity as assigned by the state or province.
Figure A.61-1: gCoreStateProvinceIdTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreStateProvinceIdType | The identifier for this entity as assigned by the state or province. | xs:normalizedString |
A state or province code. Note: When dealing with countries other than Australia, state/province codes/values other than those referenced here can be used.
Figure A.62-1: gCoreStateProvinceTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
gCoreStateProvinceType | A state or province code. Note: When dealing with countries other than Australia, state/province codes/values other than those referenced here can be used. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
infrastructureServiceNamesType | O | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
infrastructureServicesType | List | |||
infrastructureService | MR | There must be an InfrastructureService element present for each defined Infrastructure Service. The value of each InfrastructureService Property value subelement defines the URL location of that Infrastructure Service. | infrastructureServiceType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
infrastructureServiceType | xs:normalizedString | |||
@ | name | O | infrastructureServiceNamesType values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
initializationType | ||||
phaseName | O | Name of initialization phase the payload corresponds to. | xs:token | |
payload | M | Information matching the initialization phase, should result in corresponding phase having an INPROGRESS, COMPLETED, or FAILED state. | xs:anyType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
jobStateType | O | values:
|
A list of parties and data sharing permissions.
Figure A.68-1: lawListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
lawListType | A list of parties and data sharing permissions. | List | ||
law | OR | A law that applies to this contract. | lawType |
Information about the specific law.
Figure A.69-1: lawTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
lawType | Information about the specific law. | |||
lawName | M | The name of the law support is being included for. | xs:normalizedString | |
lawDescription | M | A simplified representation of a law, designed to communicate its intent to any member of the public. | xs:normalizedString |
Contains a list of the legal clauses within the contract.
Figure A.70-1: legalRequirementsTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
legalRequirementsType | Contains a list of the legal clauses within the contract. | |||
clauseList | M | A list of the legal clauses within the contract. | clauseListType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
mediaTypesType | List | |||
mediaType | MR | An Internet Media Type supported by this adaptor (for this service). | xs:token |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
messageTypeType | O | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
methodParametersType | List | |||
methodParameter | MR | Individual setting | methodParameterType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
methodParameterType | ||||
paramName | M | The name of the parameter being passed in. | xs:token | |
paramValue | M | The value of the parameter being passed in. | xs:normalizedString | |
comparisonType | O | The operation used to make the comparison. If not provided EQUAL is assumed. | xs:token |
A list of requirements imposed by the contract.
Figure A.75-1: obligationListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
obligationListType | A list of requirements imposed by the contract. | List | ||
obligation | OR | A requirement imposed by the contract. | obligationType |
A requirement imposed by the contract.
Figure A.76-1: obligationTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
obligationType | A requirement imposed by the contract. | |||
obligationDescription | O | The narrative of an individual requirement imposed by the contract. | xs:normalizedString | |
obligationURL | O | The URL pointing to the official definition of a requirment imposed by the contract. | xs:anyURI | |
benchmarkList | O | A list of benchmarks associated with the obligation. | benchmarkListType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
operationsType | List | |||
operation | MR | operationType values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
operationType | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
parametersType | List | |||
parameter | OR | Individual setting | parameterType |
Element/@Attribute | Char | Description | Type | |||||
---|---|---|---|---|---|---|---|---|
parameterType | ||||||||
name | M | The name of the query parameter to be passed in. Note: Must not conflict with any other query parameter name. | xs:token | |||||
type | O | A well understood type that MAY be used for parameter validation. Example: xs:unsignedInt. | xs:token | |||||
default | O | Value to be supplied for this parameter if the submitter omits it. | xs:token | |||||
description | O | An explanation of what this parameter represents. | xs:normalizedString
| |||||
required | O | Indicator as to if this parameter is required. If omitted, the parameter is assumed to be required!. | xs:boolean | |||||
enumerations | O | enumerationsType | ||||||
range | O | rangeType | ||||||
minLength | O | The minimum length for values of this parameter. If omitted, zero. May be functionally different because of other restrictions. | xs:unsignedInt | |||||
maxLength | O | The maximum length for values of this parameter. If omitted, unbounded. May be functionally different because of other restrictions. | xs:unsignedInt |
Who is responsible for deletion of this data?
Figure A.81-1: partyToDeleteDataTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
partyToDeleteDataType | Who is responsible for deletion of this data? | |||
organisation | O | The group responsible for ensuring the data is removed when required. | gCoreLocalIdType | |
deletecontactInfo | O | gCoreContactInfoType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
passwordEmployeeAccessStandardType | ||||
standardName | O | The label of rule set for the proceessor used to define valid passwords. | xs:normalizedString | |
standardURL | O | A link to an authoritative source for this standard. | xs:anyURI |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
phaseCollectionType | List | |||
phase | MR | phaseType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
phaseStateType | O | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
phaseType | ||||
name | M | The name of the Phase unique within the context of the owning job. | xs:token | |
states | M | A collection of the states the Phase has been through, must initially contain a NOTAPPLICABLE or NOTSTARTED state. | stateListType | |
required | M | Whether or not this phase is required for the job to complete successfully. | xs:boolean | |
rights | M | Access rights given to the consumer for this phase. | rightsType | |
statesRights | M | Access rights given to the consumer for each state. | rightsType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
privacyListType | List | |||
privacy | OR | privacyType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
privacyObligationsDocumentType | ||||
contract | O | The details of the contract the POD has been derived from. | contractType | |
legalRequirements | O | Legal Requirements Container. | legalRequirementsType | |
technicalRequirements | O | Technical Requirements Container. | technicalRequirementsType | |
dataController | O | The data controller, means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data, see GDPR. | dataControllerType | |
dataProcessor | O | The data processor, means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller, see GDPR. | dataProcessorType | |
dataSubProcessorList | O | The list of data sub-Processors who are the bodies that process data on behalf of the Data Processor. | dataSubProcessorListType |
.
Figure A.88-1: privacyTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
privacyType | . | |||
default | M | Is this the default privacy template? | values:
| |
appIDList | O | The list of applications in this contract. | appIDListType | |
adapterFingerprintList | O | A list of fingerprints. | adapterFingerprintListType | |
zoneContextList | O | A list zones and contexts where this POD applies. | zoneContextListType | |
endpointList | O | A list of endpoints that are covered by this POD. | endpointListType | |
dataModelNamespace | O | Namespace associated with the relevant datamodel. | xs:anyURI | |
dataModelVersionMin | O | Minimum data model version. | xs:normalizedString | |
dataModelVersionMax | O | Maximum data model version. | xs:normalizedString | |
privacyObligationsDocument | O | The legal and technical requirements that are required to be met to satisfy privacy and security concerns. | privacyObligationsDocumentType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
productIdentityType | ||||
vendorName | O | The name of the company supplying this Product. | xs:string | |
productName | M | The name of the Product | xs:string | |
productVersion | O | The format of this field is undefined, but it should match the format used in the agent's conformance statement, if the agent is SIF Certified. | xs:string | |
iconURI | O | HTTP URL referencing an icon for graphical representation of the application/agent. Should range from 16x16 pixels to 128x128 pixels and be of an image MIME type commonly supported by Web browsers (e.g. PNG, JPEG, GIF). | xs:anyURI |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
propertiesType | List | |||
property | MR | Individual setting | propertyType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
propertyNVListType | List | |||
property | OR | propertyNVType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
propertyNVType | ||||
propertyName | O | A short label meant to convey quick meaning of the machine readable expression. | xs:normalizedString | |
propertyValue | O | A machine readable expression designed to specify one aspect of the condition for machine enforcement. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
propertyType | xs:normalizedString | |||
@ | name | M | Name/Value pair. | xs:string |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
protocolType | ||||
location | M | The URL to use when sending Requests to a Provider | xs:anyURI | |
properties | O | May contain zero or more property elements containing name/value pairs describing any protocol settings required to ensure proper communication | propertiesType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
provisionedZonesType | List | |||
provisionedZone | MR | A specific Zone defined for this environment. | provisionedZoneType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
provisionedZoneType | ||||
@ | id | M | The unique id of the Zone, and the key to the Zone element in the Zone Registry. | xs:string |
services | O | servicesType |
A list of the purposes for which data is may be used.
Figure A.97-1: purposeListTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
purposeListType | A list of the purposes for which data is may be used. | List | ||
purpose | OR | The purpose for which data may be used. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
querySupportType | ||||
dynamicQuery | O | True if this service is capable of honoring the "where" parameter. | xs:boolean | |
queryByExample | O | True if this service is capable of honoring query by example payloads. | xs:boolean | |
changesSinceMarker | O | True if this service is capable of supporting Changes Since Queries. | xs:boolean | |
paged | O | True if this service is capable of responding to Paged Query Requests (both Interactive and Batch). | xs:boolean | |
maxPageSize | C | If Paged Queries are supported, this is the maximum number of Objects that will be returned on a Page of Query results. | xs:unsignedInt | |
totalCount | O | xs:boolean | ||
applicationProduct | C | Application Vendor Identification | productIdentityType | |
adapterProduct | O | Adapter Vendor Identification | productIdentityType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
rangeType | ||||
start | M | If a numeric range is used, this holds the inclusive starting value. | xs:long | |
end | M | If a numeric range is used, this holds the inclusive ending value. | xs:long |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
requestTypeValueType | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
rightsType | List | |||
right | MR | rightType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
rightType | rightValueType values:
| |||
@ | type | M | The type of the requested Access Right | rightTypeType values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
rightTypeType | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
rightValueType | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
securityTechnologyListType | List | |||
securityTechnology | OR | securityTechnologyType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
securityTechnologyType | ||||
clauseList | O | clauseListType | ||
technologyName | O | The name of the technology being utilized. | xs:normalizedString | |
technologyDescription | O | The narrative as to what the technology`s role is in providing security. | xs:normalizedString | |
referenceURL | O | xs:anyURI | ||
versionMin | O | The version at which the technology is considered sufficient to supply security for its applicable area. | xs:normalizedString |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
securityTestRequiredListType | List | |||
securityTestRequired | OR | Details of the security test required. | securityTestRequiredType |
Details of the security test required.
Figure A.108-1: securityTestRequiredTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
securityTestRequiredType | Details of the security test required. | |||
testType | O | Type of the test. | xs:normalizedString | |
testFrequency | O | How often does this test need to be performed? | xs:normalizedString | |
remediationRequiredIn | O | Number of days allowed to remediate any inadequacies discovered during testing. | xs:normalizedString | |
shareResults | O | Determines whether the results of a security test may be made publicly known. | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
servicesType | List | |||
service | MR | serviceType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
serviceSubTypeType | O | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
serviceType | ||||
@ | type | M | serviceTypeType values:
| |
@ | subType | O | serviceSubTypeType values:
| |
@ | name | M | The name of the Service. For utilities, this is fixed to one of the defined set of Utility Service Names. For objects and functions, it is defined by the Data Model. | xs:string |
@ | contextId | M | The unique identity of a context element, which is associated with a Provider of this name and type operating in a Zone with this ID. All Services with the same name in the same Zone must have different Context IDs. Only one such Service can have no Context. | xs:string |
rights | M | rightsType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
serviceTypeType | O | values:
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
stateCommonType | ||||
@ | id | O | uuidType | |
type | M | The type of this State object. | phaseStateType values:
| |
created | O | The datetime this job was created. | xs:dateTime | |
lastModified | O | The datetime this job was last modified. | xs:dateTime | |
description | O | A descriptive message ellaborating the condition of this state, e.g. if the state is "FAILED" the stateDescription may be "Timeout occured". | xs:string |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
stateListType | List | |||
state | MR | stateCommonType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
supportedRequestsType | List | |||
supportedRequestType | MR | The request type and supported operations available for the related service as provided by the named provider. | supportedRequestType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
supportedRequestType | ||||
requestType | O | Relay an delayed request or turn it into an immediate call. | requestTypeValueType values:
| |
operations | M | The list of operations a request can target, such as CREATE. | operationsType |
Details of technical requirements that need to be met to achieve the POD.
Figure A.118-1: technicalRequirementsTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
technicalRequirementsType | Details of technical requirements that need to be met to achieve the POD. | |||
dataAccess | O | A list of the data that can be accessed and any rules that specifically apply. | dataAccessType | |
conditionList | O | conditionListType | ||
dataSubject | O | The specific clauses obligations and benchmarks that applies to the subject - teacher, student or parent. | dataSubjectType | |
dataDeletion | O | Details and requirements for data deletion. | dataDeletionType | |
securityTechnologyList | O | securityTechnologyListType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
updatesType | List | |||
update | MR | updateType |
Element/@Attribute | Char | Description | Type | |||
---|---|---|---|---|---|---|
updateType | ||||||
@ | id | O | xs:token | |||
@ | statusCode | O | xs:token
| |||
error | O | errorCommonType |
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
uriType | O | xs:anyURI |
Element/@Attribute | Char | Description | Type | |||
---|---|---|---|---|---|---|
uuidType | O | xs:token
|
Element/@Attribute | Char | Description | Type | |||
---|---|---|---|---|---|---|
versionType | O | xs:token
|
Element/@Attribute | Char | Description | Type | |
---|---|---|---|---|
zoneContextListType | List | |||
zoneContext | OR | zoneContextType |
A Zone and/or Context related to a POD.
Figure A.125-1: zoneContextTypeElement/@Attribute | Char | Description | Type | |
---|---|---|---|---|
zoneContextType | A Zone and/or Context related to a POD. | |||
zoneId | O | Identifies the collection of appropriate data providers. | gCoreLocalIdType | |
contextId | O | Identifies the data scope within the zone. | gCoreLocalIdType |
Select shared and named code sets defined in SIF are included here for reference.
All code sets defined by external bodies and referenced within SIF are included here for reference. The left column in each table contains the individual code values that are used
in SIF elements and attributes that reference these code sets. These sets of code values are closed and normative for a given version of this specification. Including
codes not provided here in corresponding SIF elements and attributes can lead to XML validation errors in installations where the zone integration server or any agent
is validating XML messages; the SIF data model allows for locally-defined codes, where deemed appropriate, in the OtherCodeList
element. The right column of each table may provide a textual equivalent or description of the corresponding code, and is provided for informational purposes only.
The referenced sources for these code sets serve as the authorities for all descriptions and semantics, and for the definition and maintenance of the code set values themselves.
In each release of this specification the SIF Association endeavors to synchronize referenced code sets with updates from external sources.
This appendix supplies background/supplementary documentation from working groups and task forces for interested readers, including but not limited to object plans, business/use cases, test plans, test results, background and best practice documentation. Last modified dates are included in parentheses.
19 Total
125 Total
509 Total
37 Total