Appendix A: Common Types

An opaque marker that represents the amalgam of all underlying PODs tied to a specific DataProcessor-DataController relationship.

URL where the related abbreviation comes from.

Namespace where the related abbreviation comes from.

Purposes for which the data may be shared beyond its orginal uses.

A purpose for which the data may be shared beyond its orginal uses.

List of application identifiers.

The name of the software providing the services for a particular data source.

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.

The version of the SIF infrastructure which the Consumer supports.

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.

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

A List of benchmarks - where a benchmark is a set of technical or process standards to ensure the clause is met.

A benchmark is a set of technical or process standards to ensure the clause is met.

A set of technical or process standards to ensure the clause is met.

A name given to the evidence against which privacy obligations or requirements may be assessed or measured.

A unique identifier assigned to an instance of the evidence against which privacy obligations or requirements may be assessed or measured.

A description of the evidence against which privacy obligations or requirements may be assessed or measured.

A URL pointing to the evidence against which privacy obligations or requirements may be assessed or measured.

A list of the legal clauses within the contract.

Details of a legal clause within the contract.

Details of a legal clause within the contract.

A human friendly handle for refering to the associated clause.

An exact reference within the contract to a specific clause.

The actual detailed content of the clause.

List of obligations.

Official abbreviation for the given value.

URL where the related abbreviation comes from.

Namespace where the related abbreviation comes from.

What the code represents.

Human readable explanation of what the code represents.

Human readable explanation provided by the source!

The last action to be taken for this code item.

The date and time of the last action taken on this code item. So that only updates can be queried efficiently (where applicable).

Indicates the alias code has been deprecated or deleted, even if it no longer appears in the register.

Indicates the alias code is an official one; however the locale uses this one to represent that concept, at least in part.

Alternate abbreviation that might need to be more specific or correct.

The name of the parameter used fo enforce the privacy condition.

The name of the parameter used to enforce the privacy condition.

The explanation of what the related privacy conditions combine to do in plain terms.

URI associated with contract. This may be a resolvable URL or just a unique identifier.

Name associated with contract

The initial date that the contract is enforceable.

The date the contract expires and is no longer enforcable.

The version of the contract being represented by the associated elements.

List of laws covered referenced by the contract.

Who owns the intellectual property for any student under this contract.

List of impacted countries in or through which the data transits or is stored.

Name of a country impacted in or through which the data transits or is stored.

Name of a country impacted in or through which the data transits or is stored.

Country specific details about how the processor handles the data.

A list of the data that can be accessed and any rules that specifically apply.

A list of clauses that specifically apply to these technical requirements.

A list of fields that can be accessed under this POD. Equivalent to a green list.

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.

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.

URL Associated with contract

The details of the privacy contact.

The details of the individual to be contacted if there are issues in fulfilling the obligations of the contract.

Details and requirements for data deletion.

Flag indicating that the data must be deleted when no longer requred for the primary purpose.

If allowed, the length of time the data be retained when no longer required for the primary purpose.

The specific date should this data be removed from the systems.

Who is responsible for deletion of this data?

Maximum response time, number of days, for information regarding this data.

Flag indicating that the rules surrounding this data must be ported with applicable data that is transmitted.

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.

The label for the vendor who will be accessing, consuming and/or providing information back to the controller.

URL Associated with contract

The details of the privacy contact.

Indicates if the processor needs to advise the controller of access requests.

The details of the person to contact for access requests.

A list or purposes for which the data may be used.

A purpose for which the data may be shared beyond its orginal uses.

The purposes for which deidentified data is able to be used (if any).

Determines whether the data may be used for marketing purposes.

The frequency at which personal information is to be updated from source systems, including deletions.

Determines if notification of those in the breach contact list is required.

Contact details for the individual/s to be notified in the event of a data breach.

Determines whether the data controller and their staff must also comply with the privacy agreement.

Determines whether the data controller and their staff must also comply with the confidentiality agreement.

A list of the data controller employee’s training requirements.

A list of the data controller employee’s password access standards.

A list of security testing required to be completed by the data controller.

List of impacted countries in or through which the data transits or is stored.

The specific clauses obligations and benchmarks that applies to the subject - teacher, student or parent.

A list of fields that can be accessed under this POD. Equivalent to a green list.

Maximum response time, number of days, for information regarding this data.

Flag indicating that the rules surrounding this data must be ported with applicable data that is transmitted.

The list of data sub-Processors who are the bodies that process data on behalf of the Data Processor.

A data sub-Processors who are the bodies that process data on behalf of the Data Processor.

Details of organisations who process data on behalf of the data processor.

The name of the natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller.

URL Associated with contract

Details of the data sub processor`s privacy contact.

The purpose for which data is supplied to the data sub processor by the data processor.

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.

A short (possibly multi-sentence) description of the Zone

A purposes for which deidentified data may be used.

A purpose for which deidentified data may be used.

The label of the training being given to employees to teach privacy requirements and practices.

The URL of the training being given to employees to teach privacy requirements and practices.

An endpoint covered by the POD.

A type of endpoint.

The url of the endpoint.

The name of the provider of the endpoint.

Individual setting

An acceptable parameter value for this query.

If enumerated value has an equivalent code, this field may be used for conversion.

Corresponds to the value contained in the HTTPS Header Status-Code" field in which the Error Object is the payload.

Attempted operation. Ex: "Modify Student"

Indicator if the error relates to infrastructure or data.

Machine readable second code used to eliminate ambiguity.

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."

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)."

Indicator if the error relates to infrastructure or data.

Machine readable second code used to eliminate ambiguity.

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."

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)."

A list of fields that can be accessed under this POD. Equivalent to a green list.

Details of a field that can be accessed under this POD, equivalent to an element in a green list.

Details of a field that can be accessed under this POD, equivalent to an element in a green list.

The full unique path for the data field being granted access to.

The level of access being granted to the data.

A list of Address elements.

This element contains address data.

Date the address became valid.

Date the address ceases to be valid.

Address line 1.

Address line 2.

Address line 3.

The city or Suburb part of the address.

The state or province or county.

The country code.

The ZIP/postal code.

Common element used to supply information for a contact person at a school, LEA, or other institution.

The contact person`s position title.

Examples
Superintendent

Role played by this contact in this instance.

Examples
Report Contact
Primary Contact
Alternate Contact

Address of the contact.

List of Email elements.

List of PhoneNumber elements.

List of Contacts associated with an entity.

A country code or name.

A list of e-mail addresses associated with an individual or organization.

The email address.

This element represents an e-mail address of one of a number of types and occurs in objects such as StudentPersonal, StaffPersonal, StudentContactPersonal, etc..

This is a common element used to define the locally assigned identifier associated with an entity.

Core Name Type or Name elements, primarily to allow structure to be leveraged with different Type attribute values.

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.

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.

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.

All other given or middle names, each separated with a single space character.

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.

The given name preferred most by the person (as written).

Lists phone numbers associated with an entity.

This element represents a phone number and occurs within objects such as StudentPersonal, StaffPersonal, etc.

Phone number. Free-form, but typical Australian formats include:

• (###) ####-####
• ####-####
• +##### ### ###

Phone number extension.

Indicates whether or not the phone number is available to the public.

Preference number indicating an order in which phone numbers should be used when contacting person.

The identifier for this entity as assigned by the state or province.

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.

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.

Name of initialization phase the payload corresponds to.

Information matching the initialization phase, should result in corresponding phase having an INPROGRESS, COMPLETED, or FAILED state.

A list of parties and data sharing permissions.

A law that applies to this contract.

Information about the specific law.

The name of the law support is being included for.

A simplified representation of a law, designed to communicate its intent to any member of the public.

Contains a list of the legal clauses within the contract.

A list of the legal clauses within the contract.

An Internet Media Type supported by this adaptor (for this service).

Individual setting

The name of the parameter being passed in.

The value of the parameter being passed in.

The operation used to make the comparison. If not provided EQUAL is assumed.

A list of requirements imposed by the contract.

A requirement imposed by the contract.

A requirement imposed by the contract.

The narrative of an individual requirement imposed by the contract.

The URL pointing to the official definition of a requirment imposed by the contract.

A list of benchmarks associated with the obligation.

Individual setting

The name of the query parameter to be passed in. Note: Must not conflict with any other query parameter name.

A well understood type that MAY be used for parameter validation. Example: xs:unsignedInt.

Value to be supplied for this parameter if the submitter omits it.

An explanation of what this parameter represents.

Indicator as to if this parameter is required. If omitted, the parameter is assumed to be required!.

The minimum length for values of this parameter. If omitted, zero. May be functionally different because of other restrictions.

The maximum length for values of this parameter. If omitted, unbounded. May be functionally different because of other restrictions.

Who is responsible for deletion of this data?

The group responsible for ensuring the data is removed when required.

The label of rule set for the proceessor used to define valid passwords.

A link to an authoritative source for this standard.

The name of the Phase unique within the context of the owning job.

A collection of the states the Phase has been through, must initially contain a NOTAPPLICABLE or NOTSTARTED state.

Whether or not this phase is required for the job to complete successfully.

Access rights given to the consumer for this phase.

Access rights given to the consumer for each state.

The details of the contract the POD has been derived from.

Legal Requirements Container.

Technical Requirements Container.

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.

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.

The list of data sub-Processors who are the bodies that process data on behalf of the Data Processor.

.

Is this the default privacy template?

The list of applications in this contract.

A list of fingerprints.

A list zones and contexts where this POD applies.

A list of endpoints that are covered by this POD.

Namespace associated with the relevant datamodel.

Minimum data model version.

Maximum data model version.

The legal and technical requirements that are required to be met to satisfy privacy and security concerns.

The name of the company supplying this Product.

The name of the Product

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.

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).

Individual setting

A short label meant to convey quick meaning of the machine readable expression.

A machine readable expression designed to specify one aspect of the condition for machine enforcement.

Name/Value pair.

The URL to use when sending Requests to a Provider

May contain zero or more property elements containing name/value pairs describing any protocol settings required to ensure proper communication

A specific Zone defined for this environment.

The unique id of the Zone, and the key to the Zone element in the Zone Registry.

A list of the purposes for which data is may be used.

The purpose for which data may be used.

True if this service is capable of honoring the "where" parameter.

True if this service is capable of honoring query by example payloads.

True if this service is capable of supporting Changes Since Queries.

True if this service is capable of responding to Paged Query Requests (both Interactive and Batch).

If Paged Queries are supported, this is the maximum number of Objects that will be returned on a Page of Query results.

Application Vendor Identification

Adapter Vendor Identification

If a numeric range is used, this holds the inclusive starting value.

If a numeric range is used, this holds the inclusive ending value.

The type of the requested Access Right

The name of the technology being utilized.

The narrative as to what the technology`s role is in providing security.

The version at which the technology is considered sufficient to supply security for its applicable area.

Details of the security test required.

Details of the security test required.

Type of the test.

How often does this test need to be performed?

Number of days allowed to remediate any inadequacies discovered during testing.

Determines whether the results of a security test may be made publicly known.

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.

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.

The type of this State object.

The datetime this job was created.

The datetime this job was last modified.

A descriptive message ellaborating the condition of this state, e.g. if the state is "FAILED" the stateDescription may be "Timeout occured".

The request type and supported operations available for the related service as provided by the named provider.

Relay an delayed request or turn it into an immediate call.

The list of operations a request can target, such as CREATE.

Details of technical requirements that need to be met to achieve the POD.

A list of the data that can be accessed and any rules that specifically apply.

The specific clauses obligations and benchmarks that applies to the subject - teacher, student or parent.

Details and requirements for data deletion.

A Zone and/or Context related to a POD.

Identifies the collection of appropriate data providers.

Identifies the data scope within the zone.