GO-ITS 400DTS Information resource description metadata standard

1. Introduction

Government of Ontario Information Technology Standards (GO-ITS) are the official publications on the IT standards adopted through the Office of the Corporate Chief Information Officer (OCCIO) and IT Executive Leadership Council (ITELC) for use across the government’s information and information technology (I&IT) infrastructure.

These publications support the responsibilities of the Treasury Board Secretariat for coordinating standardization of I&IT in the Government of Ontario. In particular, GO-IT Standards describe where the application of an IT standard is mandatory and specify any qualifications governing the implementation of the IT standards.

1.1 Summary

1.1.1 Standard Name and Description

The Information Resource Description Metadata Standard (Metadata Standard) defines a set of common metadata elements for Ontario information resources, including data sets, publications, documents, etc. This standard would ensure that data is described consistently across the enterprise – allowing for the easy identification of critical data, and better shared understanding of Ontario’s data resources. The requirements of the Metadata Standard are based on the Dublin Core Metadata Element Set (ISO 15836), an international standard for descriptive metadata maintained by the Dublin Core Metadata Initiative. This is critical to supporting better data integration and the development of a modern data ecosystem in the province.

The standard lists metadata elements and provides requirements on how to describe each element, including the name, definition, use, refinements, obligation, repeatability and encoding scheme. It provides links to other guidance materials and resources to support a publisher working with metadata.

External links disclaimer: links provided throughout this document are intended to explain concepts in more detail. These should not be considered endorsements by the Government of Ontario, and the Government of Ontario is not responsible for content or services provided by external websites.

1.1.2 Background and Rationale

This GO-ITS is established to ensure that informational resources are described consistently throughout the enterprise and allow a collective understanding of the types of data within government datasets.

The expected benefits and results of the GO-ITS are:

• Ensuring that there is consistency of common metadata elements across the enterprise on all of Ontario’s informational resources,
• Aligning with internationally recognized metadata best practices and standards (Dublin Core Metadata Initiative), and,
• To support other government initiatives including artificial intelligence, I&IT information management and architecture, and recordkeeping.

1.1.3 Target Audience

The target audience for this document includes, but is not limited to:

• Developers
• Technical implementers
• Procurement
• Program managers

1.1.4 Scope

In scope

The scope of this document is generic metadata elements common in digital products.

Out of scope

Domain-specific metadata elements vary from product to product. Please consult domain experts.

1.2 Applicability statements

The standard applies to digital system and product design, datasets, documents, and Government of Ontario publications. It provides context of information resources to support understanding, sharing, findability, discoverability, interoperability, and reuse.

1.2.1 Organization

All Ministries and I&IT Clusters are subject to Government of Ontario IT Standards.

All adjudicative and advisory agencies are subject to Government of Ontario IT Standards.

All other agencies that are using Ontario Public Service (OPS) information and information technology products or services are required to comply with Government of Ontario IT standards if they are subject to either the Governance and Management of Information Technology Directive or Government of Ontario IT Standards by memorandum of understanding.

As new GO IT Standards are approved, they are deemed mandatory on a go-forward basis (go-forward basis means at the next available project development or procurement opportunity).

When implementing or adopting any Government of Ontario IT standards or IT standards updates, Ministries, I&IT Clusters and applicable agencies must follow their organization’s pre-approved policies and practices for ensuring that adequate change control, change management, and risk mitigation mechanisms are in place and employed. For the purposes of this document, any reference to Ministries or the Government includes applicable agencies.

More details on the application and scope specific to each type of metadata requirement are located in the introduction sections of each part.

1.2.2 Recordkeeping

With regards to metadata for managing records, this standard is not mandatory. There are recordkeeping metadata guidelines available. The OPS Recordkeeping Metadata Guideline provides advice on what metadata can be used by ministries to describe the context, content and structure of records and their management through time.

If you have any questions about this guide, you may contact the Policy, Archives and Data via email.

1.3 Privacy

Some metadata may include personal information that is defined broadly in the Freedom of Information and Protection of Privacy Act (FIPPA) as information about an identifiable individual.

As such, metadata that involves the collection, use or disclosure of personal information must be designed in accordance with the protection of privacy provisions found in Part III of FIPPA. Contact your ministry’s Freedom of Information Coordinator for more information and advice regarding FIPPA.

1.4 Metadata Element Legend

Each metadata element is described in the following way:

Element name

Definition

A statement that represents the concept and essential nature of an element.

Use

When and how an element is applied to system design, datasets, and publications. There are different levels of requirements to apply when an Information Architect builds a metadata structure.

• Must: means an absolute requirement. (New standards are not retroactive, but new standards must be complied with at the next procurement/project opportunity)
• Recommend or should: means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

Refinements

A refinement shares the meaning of a parent element but with narrower semantics. For example, ‘Date” is a parent element. “Modified” refines “Date” indicating a date on which the resource was changed.

Obligation

The obligation level of an element and, if applicable, an element’s refinements. There are different levels of requirements to fill in a metadata field.

• Required: The element or refinement must have a value.
• Optional: When a certain condition is met or when appropriate and the information is available, the element or refinement should be given a value.

Record the value for optional elements if it helps users find resources and assess the relevance to their information needs.

Repeatability

A metadata element can be used once or multiple times for a single resource. For example, Date of creation is not repeatable; a single resource can have multiple contributors. Therefore, Contributor is repeatable.

Encoding scheme

An Encoding Scheme provides contextual information or parsing rules that aid in the interpretation of a term value. Such contextual information may take the form of controlled vocabularies, formal notations, or parsing rules. There are two types of Encoding Schemes:

1. Syntax Encoding Schemes indicate that the value is a string formatted in accordance with a formal notation, such as "2000-01-01" as the standard expression of a date. 
2. Vocabulary Encoding Schemes indicate that the value is a term from a controlled vocabulary, such as the value "China - History" from the Library of Congress Subject Headings. 

Encoding scheme requirements include

• Must: is mandatory (new standards are not retroactive, but new standards must be complied with at the next procurement/project opportunity)
• Recommend or should: means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
• Example scheme: for reference purpose

2. Technical specification

2.1 Metadata Elements

This part includes a set of metadata elements that are commonly used in digital system and product design, datasets, documents, and Government of Ontario publications.

2.2 Required Common Metadata Elements

The following elements are required:

• Creator
• Date: Created
• Description
• Format
• Identifier
• Language
• Publisher
• Rights: Intellectual Property
• Subject
• Title

2.3 Summary Table: Common Metadata

2.4 Definitions: Common Metadata

1. Audience

Definition

People for whom the resource is intended or useful.

Use

Audience may be determined by the creator or the publisher or by a third party. When choosing a value from a controlled vocabulary, indicate the name of the controlled vocabulary the value was selected from.

Refinements

N/A

Obligation and repeatability

Optional, repeatable

Encoding scheme

Example scheme 1: Government of Canada Audience Scheme (archived)

• aboriginal peoples
• business
• children
• educators
• employers
• funding applicants
• general public
• government
• immigrants
• job seekers
• non-Canadians
• non-governmental organizations
• parents
• persons with disabilities
• rural community
• seniors
• students
• travellers
• veterans
• visitors to Canada
• women
• youth

Example scheme 2: Library of Congress controlled vocabulary for Audience

adolescent, adult, general, juvenile, preschool, specialized

2. Contact

Definition

The person or organization to contact with questions or comments about the resource.

Use

This element is intended for administrative purposes within the Government of Ontario. When the person to contact for information about the resource changes, the value in the element must be changed.

Refinements 

2.1 Content: The person or organization to contact with questions or comments about the intellectual content of the resource

2.2 Technical: The person or organization to contact with questions or comments about technical issues regarding the resource

Obligation and repeatability

Contact: Optional, repeatable

2.1 Content: Optional, repeatable

2.2 Technical: Optional, repeatable

Encoding scheme

The following scheme is recommended.

When specifying an organizational hierarchy, start with the largest organizational level you wish to specify.

Example:

Government of Ontario, Ministry of Transportation, Transportation Safety Division, Driver and Vehicle Services Branch, eGov@ontario.ca

When specifying an individual, express the individual’s name starting with their last name followed by a comma, then their first name. An individual’s job title may be included as well following their name.

Example:

For contact information of an individual named John Doe: Doe, John, John.Doe@ontario.ca

3. Contributor

Definition

A person or an organization responsible for contributing to the resource.

Use

It specifies a person, or organizations, or groups that contributed to the resource. Examples include but are not limited to editor, page designer, or illustrator etc.

Editor: The person, organization, or group responsible for the revision of the resource for the purposes of publication or public presentation.

Page Designer: The person responsible for designing a page.

Illustrator: The person responsible for creating an image.

Refinements

N/A

Obligation and repeatability

Contributor: Optional, repeatable

Encoding scheme

The following scheme is recommended.

When specifying an organizational hierarchy, start with the largest organizational level you wish to specify.

Example:

Government of Ontario, Ministry of Northern Development and Mines, Northern Development Division, Regional Economic Development Branch

When specifying an individual, express the individual’s name starting with their last name followed by a comma, then their first name. An individual’s job title may be included as well following their name.

Example:

For an individual named John Doe: Doe, John

4. Coverage

Definition 

The temporal, spatial, or jurisdictional extent or scope of the resource.

Use

It will typically include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity) of the content of the resource. When specifying a spatial location name, ensure that the location name is as unambiguous as possible.

Coverage refers to the temporal or spatial characteristics of the intellectual content of the resource. It is not to be confused with Common Metadata Element 11 (Location) which refers to the physical location of the resource or Common Metadata Element 6 (Date) which expresses the creation or modified date of the resource.

Coverage must be refined. See the refinements below.

Refinements

4.1 Jurisdiction: The name of the political or administrative body covered by the intellectual content of the resource.

4.2 Spatial: Spatial characteristics of the intellectual content of the resource. This refinement is not to be confused with Jurisdiction. Use ‘Spatial’ when the content of the resource refers to a geographic area that is not equivalent to a jurisdiction (e.g., Algonquin Provincial Park, Lake Superior, Niagara Escarpment)

4.3 Temporal: Temporal characteristics of the intellectual content of the resource.

Obligation and repeatability

Coverage: see refinements below

4.1 Jurisdiction: Optional, repeatable

4.2 Spatial: Optional, repeatable

4.3 Temporal: Optional, repeatable

Encoding scheme

Jurisdiction:

For names of municipalities within Ontario, a value selected from the Ministry of Municipal Affairs and Housing List of All Ontario Municipalities is recommended.

For outside Ontario, but within Canada, a value selected from Canadian Geographical Names Database (CGND) is recommended.

For outside Canada, a value selected from the Getty Thesaurus of Geographic Names (TGN) is recommended.

Spatial:

For within Ontario, visit Geographic names | ontario.ca. A value selected from the Official Geographic Names (gov.on.ca) is recommended. To view and/or download the Geographic Names Ontario (GNO) layer on the GeoHub, go to Geographic Names Ontario | Geographic Names Ontario | Ontario GeoHub (gov.on.ca).

For outside Ontario, but within Canada, a value selected from Canadian Geographical Names Database (CGND) is recommended.

For outside Canada, a value selected from the Getty Thesaurus of Geographic Names (TGN) is recommended.

Temporal:

The World Wide Web Consortium’s profile (W3CDTF) of ISO 8601:2000 "Data Elements and Interchange Formats – Information Interchange – Representation of Dates and Time" must be used. See the World Wide Web Consortium’s profile ("W3CDTF") Date and Time Formats.

• YYYY-MM-DD to express year, month, and date
• hh:mm:ss to express hour, minute, and second (am/pm not allowed) See Common Metadata Element 6 (Date) for examples.

5. Creator

Definition

A person or organization primarily responsible for making the content of the resource.

Use

It specifies the organization, individual and/or system responsible for the creation of the resource content.

Refinements

N/A

Obligation and repeatability

Required, repeatable

Encoding Schemes

The following scheme is recommended.

When specifying an organizational hierarchy, start with the largest organizational level you wish to specify.

Example:

Government of Ontario, Ministry of Transportation, Transportation Safety Division, Driver and Vehicle Services Branch

When specifying an individual, express the individual’s name starting with their last name followed by a comma, then their first name. An individual’s job title may be included as well following their name.

Example:

For an individual named Jane Doe: Doe, Jane

6. Date

Definition

A point or period of time associated with an event in the life cycle of the resource.

Use

Typically, Date will be associated with the creation or availability of the resource. The levels of granularity to be applied, from year to complete date YYYY-MM-DD plus hours, minutes, and seconds, are context specific.

Date must be refined. See refinements below.

Refinements

6.1 Available: Date that the resource became or will become available.

6.2 Created: Date of creation of the resource.

6.3 Current as of: Date that the resource was last checked for validity.

6.4 Date accepted: Date of acceptance of the resource.

6.5 Date copyrighted: Date of copyright of the resource, typically a year.

6.6 Date of next update: Date set to make changes to the resource. See related Common Metadata Element 19 (Update Frequency).

6.7 Date submitted: Date of submission of the resource.

6.8 Issued: Date of formal issuance of the resource.

6.9 Modified: Date on which the resource was changed

6.10 Valid: Date (often a range) of validity of a resource

Obligation and repeatability

Date: see refinements below

6.1 Available: Optional, repeatable

6.2 Created: Required, not repeatable

6.3 Current as of: Optional, repeatable

6.4 Date accepted: Optional, repeatable

6.5 Date copyrighted: Optional, repeatable

6.6 Date of next update: Optional, repeatable

6.7 Date submitted: Optional, repeatable

6.8 Issued: Optional, not repeatable

6.9 Modified: Optional, repeatable

6.10 Valid: Optional, repeatable

Encoding scheme

The World Wide Web Consortium’s profile ("W3CDTF") of ISO 8601:2000 "Data Elements and Interchange Formats – Information Interchange – Representation of Dates and Time" must be used.

• Complete date: YYYY-MM-DD (2023-02-24)
• Hour and minute and second: hh:mm:ss (21:06:09) am/pm not allowed
• “T” separates date from time
• Time zone designator: +hh:mm or -hh:mm

See Date and Time Formats for more details.

Examples:

October 8, 2022 at 6:59 pm Eastern Standard Time (EST): 2022-10-08T18:59-05:00

November 20, 2021 at 8:07:05 am Eastern Daylight Time (EDT): 2021-11-20T08:07:05-04:00

7. Description

Definition

An account of the resource.

Use

Description may include but is not limited to an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content. If the resource being described is an HTML web page, then both the Dublin Core "Description" metadata element and the HTML <description> meta tag must be used. The value of both the Dublin Core "Description" metadata element and the HTML<description> meta tag must be equivalent.

Refinements

N/A

Obligation and repeatability

Required, repeatable

Encoding scheme

N/A

8. Format

Definition

The file format, physical medium, or dimensions of the resource.

Use

Typically, Format may include the media-type or dimensions of the resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource.

Dimensions can include shape, size, duration, and general arrangement of information. The size or duration of the resource can be expressed in pages, data volume, linear/cubic volume, for example, 100 pages; 2 MB of textual records. Recommended practice is to specify the file size in megabytes.

Format refers to media or encoding format, for example, html, pdf, png, mov, and MP4 etc. It is not to be confused with Common Metadata Element 18 (Type) which describes the nature or genre of the content of the resource.

Refinements

N/A

Obligation and repeatability

Required, repeatable

Encoding scheme

The following schemes are recommended.

File formats: Internet Media Types (IMT) Scheme also known as MIME types

Duration: Date and Time Formats. See Common Metadata Element 6 (Date) for examples.

9. Identifier

Definition

An unambiguous reference to the resource within a given context.

Use

Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Ideally, this string or number will not change over time, and can be used to identify the same resource across different datasets and at different points in time. Example formal identification systems include the Uniform Resource Identifier (URI), including the Uniform Resource Locator (URL), the Digital Object Identifier (DOI), the International Standard Book Number (ISBN), and International Standard Serial Number (ISSN).

If the resource has been assigned an ISBN or an International Standard Book Number, then the ISBN or ISSN number is required. Identifier can also include a system generated unique identifier for the resource e.g., a Records and Document Management system unique identifier.

For information on which documents require an ISBN or ISSN and how to obtain them, refer to Intranet site Government Publications Directive and Legislative Assembly of Ontario public site ISBN and ISSN FAQs and request forms | Legislative Assembly of Ontario (ola.org).

Refinements

N/A

Obligation and repeatability

Required, repeatable

Encoding scheme

The following encoding schemes are recommended.

• Uniform Resource Identifiers (URI)
• International Standard Book Number (ISBN)
• International Standard Serial Number (ISSN)
• Digital Object Identifier (DOI)

Other encoding schemes may be used as well, such as the native identifier encoding schemes used by Content Management Systems.

10. Language

Definition

A language of the resource.

Use

Must be used for resources that have language content. If the content of the resource is multilingual, repeat the language element for each language used. When the content of the same resource exists in multiple languages, declare the language for each; use the refinements HasVersion and IsVersionOf of Common Metadata Element 14 (Relation) to describe how they relate to each other.

Refinements

N/A

Obligation and repeatability

Required, Repeatable

Encoding scheme

ISO639-2 Codes for the representation of names of languages must be used.

Examples: eng, fre

The three-letter language code can be followed by an optional three letter country code. Language code is given in lowercase. Country code is given in uppercase, e.g., fre; CAN.

For a resource in American Sign Language (ASL), use the code “sgn-US”.

For a resource in La langue des signes québécoise (LSQ), use the code “ sgn-CA-QC ”.

11. Location

Definition

The physical location of the resource.

Use

This element enables the physical form of the resource to be found. It is only for resources in physical form (for example, paper files, books, CD/DVD, Audio/Video tapes, and photographs).

This element is not to be confused with Spatial, the refinement of Common Metadata Element 4 (Coverage). Spatial refers to the characteristics of the content of the resource.

Refinements

N/A

Obligation and repeatability

Optional, repeatable

Encoding scheme

Where the location is described using a Physical Address or Electronic Address (as defined in the OPS Common Data Elements Model), leverage the guidance available at the logical level in the CDEM for 'Address', i.e., to fully describe an address of the physical or virtual location where the resources are placed and can be retrieved.

Note: For electronic digital-only address purposes, e.g., file paths, file folder virtual locations, digital document management solutions, etc., consult with information architecture specialists in your IT support cluster.

Where the location of the resource needs to be human readable, write out the physical address as in the XML example for Location in Appendix II.

Where the location involves shelf numbers, room names, etc., create a local encoding scheme.

12. Mandate

Definition

A statutory authority that requires the resource to be created or provided.

Use

Use this element to indicate the specific legal mandate that requires the resource to be created or provided to the public. The content of this element should be a reference to a legal instrument such as an Act, Regulation or Contract.

Refinements

N/A

Obligation and repeatability

Optional, repeatable

Encoding scheme

N/A

13. Publisher

Definition

A person or an organization responsible for making the resource available.

Use

Publisher must be populated with the name of an organization and/or group responsible for making the resource available in its current form.

Refinements

N/A

Obligation and repeatability

Required, repeatable

Encoding scheme

The following scheme is recommended.

When specifying an organizational hierarchy, start with the largest organizational level you wish to specify

Example:

Government of Ontario, Ministry of Transportation, Transportation I&IT Cluster, Highways and Business Services Application Solutions Branch

When specifying an individual, express the individual’s name starting with their last name followed by a comma, then their first name

Example:

For an individual named John Doe: Doe, John

14. Relation

Definition

A related resource.

Use

The best practice is to reference the resource by means of a string or number conforming to a formal identification system.

Relation must be refined. See the refinements below.

Refinements

14.1 Conforms to: An established standard to which the described resource conforms.

14.2 Has format: A related resource that is substantially the same as the pre-existing described resource, but in another format.

14.3 Is format of: A pre-existing related resource that is substantially the same as the described resource, but in another format.

14.4 Has part: A related resource that is included either physically or logically in the described resource.

14.5 Is part of: A related resource in which the described resource is physically or logically included.

14.6 Has version: A related resource that is a version, edition, or adaptation of the described resource. Examples include but are not limited to an adaption or a translation.

Adaption: The described resource in the source language has an adapted version in the target language, namely the referenced resource.

Translation: The described resource in the source language has a translated version in the target language.

14.7 Is version of: A related resource of which the described resource is a version, edition, or adaptation. Changes in version imply substantive changes in content rather than differences in format. For example, the described resource is an adaptation or a translation of the original resource.

14.8 References: A related resource that is referenced, cited, or otherwise pointed to by the described resource.

14.9 Is referenced by: A related resource that references, cites, or otherwise points to the described resource.

14.10 Replaces: A related resource that is supplanted, displaced, or superseded by the described resource.

14.11 Is replaced by: A related resource that supplants, displaces, or supersedes the described resource.

14.12 Requires: A related resource that is required by the described resource to support its function, delivery, or coherence.

14.13 Is required by: A related resource that requires the described resource to support its function, delivery, or coherence.

Obligation and repeatability

Relation: Optional, repeatable

14.1 Conforms to: Optional, repeatable

14.2 Has format: Optional, repeatable

14.3 Is format of: Optional, repeatable

14.4 Has part: Optional, repeatable

14.5 Is part of: Optional, repeatable

14.6 Has version: Optional, repeatable

14.7 Is version of: Optional, repeatable

14.8 References: Optional, repeatable

14.9 Is referenced by: Optional, repeatable

14.10 Replaces: Optional, repeatable

14.11 Is replaced by: Optional, repeatable

14.12 Requires: Optional, repeatable

14.13 Is required by: Optional, repeatable

Encoding scheme

Has version and Is version of

If possible, include a reference to the translated resource, the adapted resource, and the original resource by indicating its URL, URI or other unique identifier. When specifying the language of the intellectual content of a referenced resource, ISO639-2 Codes for the representation of names of languages must be used.

Has format and Is format of

See Common Metadata Element 8 (Format). If possible, include a reference to a resource available in another format and the original source by indicating its URL, URI or other unique identifier.

15. Rights

Definition

Information about rights held in and over the resource.

Use

Typically, a Rights element will contain a rights management statement for the resource or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, access rights and various Property Rights. If the Rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource.

Rights must be refined. See the refinements below.

Refinements

15.1 Access rights: Information about who can access, edit, and/or delete the resource or an indication of its security status.

Use: The value of Access Rights could include the privileges of a group, a role, or individuals. Access rights may include information regarding access or restrictions based on privacy, security, or other regulations. Refer to OPS Corporate Policy on Cyber Security and Cyber Risk Management.

15.2 Information classification level: The sensitivity value of the resource from the information classification policy.

15.3 Intellectual property: Use to express trademark and/or patent and/or copyright notices as applicable.

Obligation and repeatability

Rights: see refinements below

15.1 Access rights: Optional, repeatable

15.2 Information classification level: Optional, not repeatable (If the resource has been assigned a sensitivity level of Low, Medium, or High, the refinement must record the assigned value.)

15.3 Intellectual property: Required, repeatable

Encoding scheme

Information Classification Level

Must use the sensitivity values from Corporate policy on information sensitivity classification | ontario.ca. Levels of sensitivity classification include:

• High Sensitivity
• Medium Sensitivity
• Low Sensitivity
• Unclassified

16. Subject and key words

Definition

topic(s) of the resource.

Use

Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.

If the resource being described is an HTML web page, then both the Dublin Core "Subject" metadata element and the HTML <keywords> meta tag must be used. <keywords> may include natural language terms that have not been selected from a controlled vocabulary, but the terms used to populate<keywords> must at least include the controlled terms used to populate the Dublin Core "Subject" metadata element.

Refinements

N/A

Obligation and repeatability

Subject: Required, repeatable

Key words: Optional, repeatable

Encoding scheme

Recommended best practice is to choose subject terms from an approved controlled vocabulary. Repeat the subject element if you are choosing terms from more than one controlled vocabulary.

Example scheme:

Government of Canada Core Subject Thesaurus - Search the Thesaurus (multites.net)

17. Title

Definition

A name given to the resource.

Use 

Typically, a Title will be a name by which the resource is formally known. If the resource is an HTML web page, then the content of "Title" must match the content of the HTML <title> tag.

Refinements

17.1 Alternative: A substitute or another title available besides the formal title of the resource.

Use: Alternative can include Title abbreviations. To express translated resources, use the refinements of Common Metadata Element 11 (Relation) HasVersion and IsVersionOf.

Obligation and repeatability

Title: Required, repeatable

17.1 Alternative: Optional, repeatable

Encoding scheme

Branches, departments, program areas or project teams may define their own resource title formats.

18. Type

Definition

The nature or genre of the resource.

Use

Type includes terms describing general categories, functions, genres or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary. The element is not to be confused with Common Metadata Element 8 (Format) which describes the physical or digital manifestation of the resource.

Refinements

N/A

Obligation and repeatability

Optional, repeatable

Encoding scheme

Recommended best practice is to select a value from an approved controlled vocabulary list. OPS Government of Ontario Type Scheme is recommended.

• Agendas
• Agreements
• Annual Reports
• Backgrounders
• Bulletins and Notices
• Calendars
• Conferences
• Events
• Financial Reports
• Forms
• Geographic Data
• Geographic Information Systems
• Mandate Letters
• Manuals and Guidelines
• Maps
• Meetings
• Minutes and Decisions
• News Releases
• Newsletters
• Policies and Directives
• Policy and Discussion Papers
• Promotional and Educational Material
• Public Consultations
• Reports
• Speeches and Speaking Notes
• Standards and Codes
• Statistics and Data
• Strategic Plans

19. Update frequency

Definition

The frequency with which changes and additions are made to the resource after the initial resource is completed.

Use

Choose the applicable frequency as appropriate. Depending on business needs, commonly used Frequency options include ‘Continual’, ‘Annually’, ‘As Needed’, ‘As required’, and ‘Not Planned’ etc. For a specific date scheduled for an update, see Common Metadata Element 6.6 (Date of next update).

Refinements

N/A

Obligation and repeatability

Optional, repeatable

Encoding scheme

N/A

20. Version

Definition

Number or name of the version, edition, release, or revision of the resource.

Use

Branches, departments, program areas, project teams or individuals may define their own resource version numbering conventions. To express subsequent/prior versions to each other, use the refinements of Common Metadata Element 14 (Relation): hasVersion and IsVersionOf.

Refinements

N/A

Obligation and repeatability

Optional, not repeatable

Encoding scheme

N/A

3. Related standards and impacted infrastructure

3.1 Impacts to existing standards

3.2 Impacts to existing infrastructure

3.3 Compliance requirements

In order to manage the effectiveness and implementation of this standard, Ministries, I&IT Clusters and applicable agencies are expected to adopt and monitor compliance.

3.4 Roles and Responsibilities

Accountable Role (Standard Owner) Definition:       
The individual or committee ultimately accountable for the effectiveness of a standard and for its full life- cycle, including development, reviews, revisions, updates, evaluations, and rescindment. Where a committee owns the standard, the committee Chair is accountable for the standard. There must be exactly one accountable role identified.

Accountable Role:       
Title: Director, Governance and Standards
Ministry/I&IT Cluster: Ministry of Public and Business Service Delivery and Procurement Division: Policy, Archives and Data; Enterprise Data Stewardship Division       
Branch: Governance and Standards Branch

Responsible Role Definition       
The organization(s) responsible for the development of this standard. There may be more than one responsible organization identified if it is a partnership/joint effort. (Note: the responsible organization(s) provides the resource(s) to develop the standard).

Responsible Organization(s):       
Ministry/I&IT Cluster: Ministry of Public and Business Service Delivery and Procurement Division: Enterprise Data Stewardship Division       
Branch: Governance and Standards Branch

Support Role Definition       
The support role is the resource(s) to whom the responsibility for maintaining this standard has been assigned. Inquiries, feedback, and suggestions should be sent to this resource.

Support Role (Editor):
Ministry/I&IT Cluster: Ministry of Public and Business Service Delivery and Procurement Division: Policy, Archives and Data; Enterprise Data Stewardship Division       
Job Title: Senior Manager, Governance and Standards Branch 
Name: Andre Breau
Phone: (416) 575-2358 
Email: andre.breau@ontario.ca

3.5 Consultations

Areas consulted as part of the development of this standard. Include individuals and committees, councils and/or working groups:

3.6 Document history

4. Glossary

Controlled vocabulary:

A controlled vocabulary is a carefully selected, pre-determined list of words and phrases, which are used to tag units of information (document or work) so that they may be more easily retrieved by a search. Controlled vocabularies solve the problem of synonyms, where different people use different words to refer to the same concept. Thesauri and subject heading schemes are examples of controlled vocabularies. It is developed by Taxonomist, Ontologist, or Information Architect, applied by Indexer, Cataloger or Metadata Specialist, and used by searchers or users to seek information.

Dublin Core Metadata Initiative (DCMI):

An open forum engaged in the development of interoperable online metadata standards that support a broad range of purposes and business models.

Dublin Core Metadata Element Set (DCMES):

A set of 15 Metadata Elements developed by the Dublin Core Metadata Initiative.

DCMI Metadata Terms:

All metadata terms maintained by the Dublin Core Metadata Initiative (DCMI) including metadata elements, element refinements, encoding schemes, and vocabulary terms.

Element:

A property of a resource. "Properties" are attributes of web resources – characteristics that a web resource may "have", such as a Title, Creator or Subject.

Entity:

An individual or an organization.

Encoding Scheme:

An Encoding Scheme provides contextual information or parsing rules that aid in the interpretation of an element or refinement’s value. Such contextual information may take the form of controlled vocabularies, formal notations, or parsing rules.

Government of Ontario Web Metadata Element Set (GO-WMES):

The common set of metadata elements and element refinements for describing Government of Ontario web resources. The GO-WMES is based on the Dublin Core Metadata Element Set and the DCMI Metadata Terms.

Interoperability:

"the ability of two or more systems or components to exchange descriptive data about things, and to interpret the descriptive data that has been exchanged in a way that is consistent with the interpretation of the creator of the data" (Mikael Nilsson)

Metadata:

Data that describes data and that enables collaboration and interoperability.

Refinement:

An Element Refinement is a property of a resource that shares the meaning of a particular metadata element but with narrower semantics.

Repeatability:

A metadata element can be used once or multiple times for a single resource. For example, Date of creation is not repeatable; Contributor is, because a single resource can have multiple contributors.

Semantics:

Significance or meaning. In the case of Dublin Core, the significance or intended meaning of individual metadata elements and their components.

Syntax Encoding Scheme:

Syntax Encoding Schemes indicate that the value is a string formatted in accordance with a formal notation, such as "2004-01-01" as the standard expression of a date.

Uniform Resource Identifier (URI):

The generic term for all types of names and addresses that refer to objects on the World Wide Web. URI include both URL and URN.

Uniform Resource Locator (URL):

A unique address for a resource accessible on the World Wide Web. A URL consists of an access protocol and a server domain name and may also include the access path to a web resource found on the server. A URL is a type of Uniform Resource Identifier (URI).

Uniform Resource Name (URN):

A URI that has some assurance of persistence beyond that normally associated with an Internet domain or host name. A URN is not location dependent.

Vocabulary Encoding Scheme:

Vocabulary encoding schemes indicate that a metadata element or a refinement’s value is a term from a controlled vocabulary, such as the value "Architectural Heritage" from the Government of Canada’s Core Subject Thesaurus.

Appendix 1: References and Resources

Normative references

Dublin Core Metadata Initiative:
Dublin Core Metadata Initiative (DCMI)

OPS Governance and Management of Information Technology Directive

GO IT Standards:       
https://www.ontario.ca/government/information-technology-standards

Note: a normative reference specifies a supporting document or GO IT Standard (in the case of the Government of Ontario's I&IT infrastructure, often another OPS I&IT authorized publication) that must be read to fully understand or implement the subject matter of the main GO IT Standard. Such authoritative or de facto references may be external and may, or may not be, owned/controlled by the GO IT Standard owner.

Informative references

Further Resources

• Corporate policy on information sensitivity classification | ontario.ca
• Copyright information: © King's Printer for Ontario | ontario.ca
• Freedom of Information and Protection of Privacy Act 
• Government of Canada Core Subject Thesaurus - Search the Thesaurus (multites.net)
• Government Publication Directive
• Internet Media Types (IMT) Scheme (also known as MIME types)
• Natural Resources Canada. (2018, December 6). Digital Geospatial Metadata. Retrieved from Digital Geospatial Metadata
• OPS Recordkeeping Metadata Guideline

Related Standards

The following standards are to be considered in conjunction with this standard.

• Digital Service Standard
• ISO Standard 639-2 (three-character bibliographic language codes)
• ISO 639-2: Codes for the Representation of Names of Languages
• ISO 15836-2003: Information and documentation – The Dublin Core metadata element set (revised by ISO 15836-1:2017 and ISO 15836-2:2019 )
• The World Wide Web Consortium’s profile of ISO 8601:2000 "Data Elements and Interchange Formats – Information Interchange – Representation of Dates and Time":

References

This standard is built from other jurisdictions, including:

• Digital Object Identifier (DOI) System
• Dublin Core Metadata Initiative (DCMI)
• Dublin Core Metadata Element Set (DCMES) Version 1.1
• DCMI Metadata Terms
• DCMI Glossary
• DCMI Registry
• DCMI Guidelines for implementing in XML
• International Standard Book Number (ISBN)
• International Standard Serial Number (ISSN)
• NISO Standard Z39.85-2001

Note: an informative reference is not normative; rather, it provides only additional background information.

Appendix 2: Dublin Core Terms Mapping

Appendix 3: HTML and XML example for common metadata

The XML examples below are encoded according to the Guidelines for implementing Dublin Core in XML recommended by the DCMI http://dublincore.org/specifications/dublin-core/dc-xml-guidelines/.

Web Resource refers to an information resource addressable via a Uniform Resource Locator (URL). Web pages, digitized images, sound files, videos or any other information resources available on Internet, Intranet or Extranet websites are examples of web resources.

1. Audience

HTML examples

For a web resource intended for seniors:

<meta name="dcterms.audience" content="Seniors" />

For a web resource intended for persons looking for a job where the value has been chosen from the Government of Canada Audience Scheme:

<meta name="dcterms.audience" scheme="gcaudience" content="job seekers" />

XML examples

For an information resource containing information about government services for aboriginal peoples, where the value "Aboriginal Peoples" has been chosen from the Government of Canada Audience Scheme.

<dcterms:audience xsi:type="gcaudience">Aboriginal Peoples</dcterms:audience>

2. Contact

HTML examples

The general contact for a web resource:

<meta name="go.contact" content=" Government of Ontario, Ministry of Transportation, Transportation Safety Division, Driver and Vehicle Services Branch, eGov@ontario.ca" />

For a web resource with an email address for technical support:

<meta name="go.contact.technical content="support@ontario.ca" />

For a web resource with an individual to contact with questions regarding the intellectual content of the web resource:

<meta name="go.contact.content" content="Doe, John, John.Doe@ontario.ca" />

XML examples

For the contact person for the data being described:

<go:contact>Doe, Jane, Technical Specialist, Government of Ontario, Ministry of Transportation, Government of Ontario, Ministry of Transportation, Transportation Safety Division, Driver and Vehicle Services Branch </go:contact>

For the general contact for a web resource:

<go:contact>Government of Ontario, Ministry of Transportation, Government of Ontario, Ministry of Transportation, Transportation Safety Division, Driver and Vehicle Services Branch, website.contact@ ontario.ca</go:contact>

3. Contributor

HTML examples

For a web resource that received input from, but was not created by, the Regional Economic Development Branch of the Ministry of Northern Development and Mines, for example, editing, page design or embedding images:

<meta name="dc.contributor" content="Government of Ontario, Ministry of Northern Development and Mines, Northern Development Division, Regional Economic Development Branch" />

XML examples

For an information resource that was written by the Ministry of Natural Resources, with input and advice from the Drinking Water Program Management Branch:

<dc:contributor>Government of Ontario, Ministry of Environment, Drinking Water Management Division, Drinking Water Program Management Branch</dc:contributor>

4. Coverage

HTML examples

For a web resource whose content applies to the Province of Ontario:

<meta name="dc.coverage.jurisdiction" content="Ontario, Canada" />

For a web resource whose content applies to the Region of Peel:

 <meta name="dc.coverage.jurisdiction" content="Region of Peel, Ontario, Canada" />

For a web resource whose content applies to the region known as the Greater Toronto Area:

<meta name="dc.coverage.spatial" content="Greater Toronto Area" />

For a web resource whose content is about events that occurred between January 1st, 2021 and December 31st, 2022:

<meta name="dc.coverage.temporal" scheme="W3CDTF" content="2021-01-01/2022-12-31" />

For a web resource whose content is about the time period known as "The Renaissance":

<meta name="dc.coverage.temporal" content="The Renaissance" />

XML examples

Jurisdiction

For a news release that applies to the Province of Ontario:

<go:jurisdiction>Province of Ontario</go:jurisdiction>

For a report about a project in Temagami:

<go:jurisdiction>Municipality of Temagami</go:jurisdiction>

Spatial

For an information resource about Algonquin Park where a value is selected from the Ontario Geographic Names Database:

<dcterms:spatial>Algonquin Provincial Park</dcterms:spatial>

Temporal

For a report about a project that existed from May 1, 2019 through March 31, 2022

<dcterms:temporal xsi:type="dcterms:W3CDTF">2019-05-01/2022-03-31 </dcterms:temporal>

5. Creator

HTML examples

For a web resource created by the Highways and Business Services Application Solutions Branch of the Ministry of Transportation:

<meta name="dc.creator" content="Government of Ontario, Ministry of Transportation, Transportation I&IT Cluster, Highways and Business Services Application Solutions Branch" />

For a web resource created by the Veterinary Science branch of the Ministry of Agriculture and Food:

<meta name="dc.creator" content="Government of Ontario, Ministry of Agriculture and Food, Agriculture and Food Division, Livestock Technology, Veterinary Science" />

For a web resource created by an individual named Jane Doe:

<meta name="dc.creator" content="Doe, Jane" />

For a web resource created by an external consulting firm:

<meta name="dc.creator" content="GovConsultants Inc." />

XML examples

For an information resource that was created by Stakeholder Relations and Policy Development in the Ontario Women’s Directorate:

<dc:creator> Government of Ontario, Ministry of Citizenship and Immigration, Ontario Women’s Directorate, Office of the Executive Director, Stakeholder Relations and Policy Development</dc:creator> 

6. Date

HTML examples

For a web resource available on October 8, 2022 at 6:59 pm Eastern Standard Time (EST):

<meta name="dc.date.available" scheme="W3CDTF" content="2022-10-08T18:59-05:00" />

For a web resource available on November 20, 2022 at 6:00 pm Eastern Daylight Time (EDT):

<meta name="dc.date.available" scheme="W3CDTF" content="2022-11-20T18:00-04:00" />

For a web resource created on March 17, 2022:

<meta name="dc.date.created" scheme="W3CDTF" content="2022-03-17" />

For a web resource created on March 17, 2022 but first published to the web on April 10, 2022:

<meta name="dc.date.created" scheme="W3CDTF" content="2022-03-17" />

<meta name="dc.date.issued" scheme="W3CDTF" content="2022-04-10" />

For the same resource later updated on August 28, 2022:

<meta name="dc.date.created" scheme="W3CDTF" content="2022-03-17" />

<meta name="dc.date.modified" scheme="W3CDTF" content="2022-08-28" />

For a web resource copyrighted on November 20, 2020:

<meta name="dc.date.copyrighted" scheme="W3CDTF" content="2020-11-20" />

For a web resource with the date of next update on November 03, 2022 at 11:59pm Eastern Daylight Time (EDT):

<meta name="go.dateofnextupdate" scheme="W3CDTF" content="2022-11-03T23:59-04:00" />

For a web resource valid between September 17, 2021 and September 17, 2022:

<meta name="dc.date.valid" scheme="W3CDTF" content="2021-09-17/2022-09-17" />

XML examples

For an information resource that was created on December 3, 2004:

<dcterms:created xsi:type="dcterms:W3CDTF">2004-12-03</dcterms:created>

For a web resource copyrighted on November 20, 2020:

<dcterms:copyrighted xsi:type="dcterms:W3CDTF">2020-11-20</dcterms: copyrighted> 

For an information resource that was last checked for validity on May 15, 2005, but was not modified:

<go:currentAsOf xsi:type="dcterms:W3CDTF">2005-05-15</go:currentAsOf> 

For a web resource that was first published to the web on August 2, 2005:

 <dcterms:issued xsi:type="dcterms:W3CDTF">2005-08-02</dcterms:issued>

For an information resource that was modified on January 3, 2005:

<dcterms:modified xsi:type="dcterms:W3CDTF">2005-01-03</dcterms:modified">

For an information resource that is valid for the 2005/2006 Fiscal year:

<dcterms:valid xsi:type="dcterms:W3CDTF">2005-04-01/2005-03-31</dcterms:valid>

For a web resource with the date of next update on November 3, 2022 at 11:59pm Eastern Daylight Time (EDT): 

<go: dateOfNextupdate xsi:type="dcterms:W3CDTF">2022-11-03T23:59-04:00</go: dateOfNextupdate >

7. Description

HTML examples

For a description of the Government of Ontario’s central website:

<meta name="dc.description" content="The official home page of the Government of the Province of Ontario, Canada." />

XML examples

For the ‘Finding a Job’ Life Event Bundle found on the Government of Ontario’s central website:

<dc:description>How to find a job in Ontario, Canada. Employment information and strategies.</dc:description>

8. Format

HTML examples

For an HTML web page:

<meta name="dc.format" scheme="IMT" content="text/html" />

For an Adobe® PDF document posted on the web:

<meta name="dc.format" scheme="IMT" content="application/pdf" />

For a Microsoft® Word document posted on the web:

<meta name="dc.format" scheme="IMT" content="application/msword" />

XML examples

For a Portable Document Format (PDF) document where the value is selected from the IMT Scheme:

<dc:format xsi:type="dcterms:IMT">application/pdf</dc:format>

For a Corel WordPerfect® Document where the value is selected from the Government of Canada Format Scheme:

<dc:format xsi:type="gcformat">application/x-corel-wordperfect</dc:format>

9. Identifier

HTML examples

For an HTML web page:

<meta name=”dc. identifier” scheme=”URI” content=”http://www.gov.on.ca”/>

For a web resource that has been assigned an ISBN number:

 <meta name=”dc. identifier” scheme=”ISBN” content=”0-123456-78-9”/>

XML examples

For a publication that has been assigned an ISBN:

<dc: identifier xsi :type = “ISBN”> 0-7794-0000-0 <dc: identifier > 

10. Language

HTML examples

For a web resource in English:

<meta name="dc.language" scheme="ISO629-2" content="eng" />

For a web resource in French:

<meta name="dc.language" scheme="ISO629-2" content="fre" />

For a web resource in both English and French:

<meta name="dc.language" scheme="ISO629-2" content="eng" />
<meta name="dc.language" scheme="ISO629-2" content="fre" />

XML examples

For an information resource in English:

<dc:language xsi:type="ISO639-2">eng</dc:language>

For an information resource in French:

<dc:language xsi:type="ISO639-2">fre</dc:language>

For a multi-lingual information resource with English, French and Inuktitut in the same resource:

<dc:language xsi:type="ISO639-2">eng</dc:language>
<dc:language xsi:type="ISO639-2">fre</dc:language>
<dc:language xsi:type="ISO639-2">iku</dc:language>

11. Location 

HTML examples

For a resource located in a reference library at 250 Yonge Street, 16^th Floor, ESDI Lab–reference library, Toronto, Ontario

<meta name="go.location" content="250 Yonge Street, 16th Floor, ESDI Lab–reference library, Toronto, Ontario" />

XML examples

For a resource located in a reference library:

<go:location>250 Yonge Street, 16th Floor, ESDI Lab–reference library, Toronto, Ontario </go:location> 

12. Mandate

HTML examples

For a web resource that has been produced by order of an Act of Parliament:

<meta name="go.mandate" content="Automobile Insurance Rate Stabilization Act, 2003" />

XML examples

For data that is required to be collected according to the Environmental Protection Act:

<go:mandate>Environmental Protection Act, R.S.O. 1990, c. E.19</go:mandate>

13. Publisher

HTML examples

For a web resource published by the Ministry of Culture’s Public Relations unit:

<meta name="dc.publisher" content="Government of Ontario, Ministry of Culture, Deputy Minister, Communications Branch, Public Relations Unit" />

For a web resource jointly published by the Ministry of Citizenship and Immigration and the Government of Canada:

<meta name="dc.publisher" content="Government of Ontario, Ministry of Citizenship and Immigration" />

<meta name="dc.publisher" content="Government of Canada" />

XML examples

For a resource published by the Policy and Public Safety Programs Division of the Ministry of Community Safety and Correctional Services:

<dc:publisher>Government of Ontario, Ministry of Community Safety and Correctional Services, Community Safety, Policy and Public Safety Programs Division</dc:publisher>

14. Relation

HTML examples

For a web resource that has a related news release:

<meta name="dc.relation" content="News Release, http://www.gov.on.ca/FIN/english/media/2004/nre9-maple.htm" />

For a web resource that conforms to a known standard:

<meta name="dc.relation.conformsTo" content="GO-ITS 23 - World Wide Web - Content Standard" />

For an HTML web resource also available as an Adobe® PDF document:

<meta name="dc.relation.hasFormat" content="http://www.gov.on.ca/FIN/english/economy/statement04/04fs-eng.pdf" /> 

For a web resource also available in French:

<meta name="dc.relation.hasVersion" lang="fre" content="Loi sur l’accès à l’information et la protection de la vie privée, http://www.e-laws.gov.on.ca/DBLaws/Statutes/French/90f31_f.htm" /> 

For a web resource that is a French translation of an English web resource:

<meta name="dc.relation.isVersionOf" lang="eng" content="Freedom of Information and Protection of Privacy Act, http://www.e-aws.gov.on.ca/DBLaws/Statutes/English/90f31_e.htm" /> 

For a French adaptation of the Ontario Health and Physical Education Curriculum for Grades 1-8:

<meta name="dc.relation.isVersionOf" lang="eng" content="Health and Physical Education, The Ontario Curriculum, Grades 1-8, 1998, http://www.edu.gov.on.ca/eng/document/curricul/health/healthe.html" />

For a web resource that makes reference to the Dublin Core Metadata Element Set:

<meta name="dc.relation.references" content="Dublin Core Metadata Terms, http://dublincore.org/documents/dces/" /> 

For a web resource that replaces another existing resource:

<meta name="dc.relation.replaces" content="Web Metadata Working Group Terms of Reference Version 1.1" />

XML examples

Has format

For an HTML page that also exists in Adobe® PDF format:

<dcterms:hasFormat>http://www.fin.gov.on.ca/english/budget/bud05/statement.pdf</dcterms:hasFormat>

Is format of

For an Adobe® PDF document that contains the same intellectual content as an HTML page:

<dcterms:isFormatOf> http://www.fin.gov.on.ca/english/budget/bud05/statement.html </dcterms:isFormatOf>

Has part 

For the Ministry of Natural Resources energy project files Ontario (Government Record Series RG 1-265) containing a file entitled ‘Biomass Wood Studies’:

<dcterms:hasPart> Biomass Wood Studies</dcterms:hasPart>

Is part of

For the ‘Biomass Wood Studies’ file that is part of the Ministry of Natural Resources energy project files record series:

<dcterms:isPartOf> Ministry of Natural Resources energy project files, Ontario Government Record Series RG 1-265</dcterms:isPartOf> 

Has version ( example 1)

For a resource also available in French:

<dcterms:hasVersion :lang="fre">Loi sur l'accès à l'information et la protection de la vie privée, http://www.e-laws.gov.on.ca/DBLaws/Statutes/French/90f31_f.htm</dcterms:hasVersion>

Is version of (example 1)

For a web resource that is a French translation of an English web resource:

<dcterms:isVersionOf xml:lang="eng"> Freedom of Information and Protection of Privacy Act, http://www.e-laws.gov.on.ca/DBLaws/Statutes/English/90f31_e.htm </dcterms:isVersionOf> 

Has version (example 2)

For a web resource describing Ontario's climate that has an adaptation in French:

<dcterms:hasVersion xml:lang="fre">Climat - Géographie -l'Ontario en bref (Gouvernement de l'Ontario, Canada), http://www.gov.on.ca/ont/portal/!ut/p/.cmd/cs/.ce/7_0_A/.s/7_0_252/_s.7_0_A/7_0_252/_l/fr?docid=004782</dcterms:hasVersion>

Is Version Of (example 2)

For a French adaptation of the Ontario Health and Physical Education Curriculum for Grades 1-8:

<dcterms:isVersionOf xml:lang="eng">Health and Physical Education, The Ontario Curriculum, Grades 1-8, 1998</dcterms:isVersionOf>

15. Rights

HTML examples

For a web resource intended for Ontario Public Service staff only:

<meta name="dc.rights.accessRights" content="Restricted to Ontario Public Service Employees" />

The copyright notice for a Government of Ontario web resource:

<meta name="dc.rights.intellectualProperty" content="Copyright Queen’s Printer for Ontario, 2005, http://www.gov.on.ca/MBS/english/common/queens.html" />

For a web resource that has been assigned a value of "Low Sensitivity" from the OPS Corporate Policy on Information and Information Technology (I&IT) Security:

<meta name="dc.rights.informationClassificationLevel" content="Low Sensitivity" />

XML examples

Access rights

For an information resource that is restricted to Ontario Public Service Staff only:

<dcterms:accessRights>Restricted to Ontario Public Service Employees </dcterms:accessRights>

Information classification level

For a document that is classified as Medium Sensitivity according to the OPS Corporate Policy on Information and Information Technology (I&IT) Security:

 <go:sensitivity>Medium Sensitivity</go:sensitivity>

Intellectual property

The copyright notice for a Government of Ontario publication:

<go:intellectualProperty>Copyright King’s Printer for Ontario, 2023<go:intellectualProperty> 

16. Subject and key words

HTML examples

For an HTML web resource with multiple subject terms chosen from the "abc" controlled vocabulary:

<meta name="dc.subject" scheme="abc" content="Tourism; Toronto; Ontario" />
<meta name="keywords" content="Tourism; Toronto; Ontario; Travelling; Visiting Toronto" />

For an HTML web resource with subjects chosen from multiple controlled vocabularies:

<meta name="dc.subject" scheme="gccore" content="Nutrition; Vitamins; Cooking" />
<meta name="dc.subject" scheme="cv" content="Eating Right; Healthy Living" />

<meta name="keywords" content="Nutrition, Vitamins, Cooking, Eating Right, Healthy Living" />

XML examples

For an information resource about nutrient management where a value is selected from ABC-Thesaurus;

<dc:subject xsi:type="abcthesaurus">Nutrient Management</dc:subject> 

For an information resource about highway safety where two values were selected from ABC-Thesaurus, and one value was selected from the Government of Canada Core Subject Thesaurus:

<dc:subject xsi:type="abcthesaurus">Highway Safety, Highway Policing </dc:subject> <dc:subject xsi:type="gccore">Road Safety</dc:subject>

17. Title

HTML examples

For the Government of Ontario’s central site:

<title>Government of Ontario, Canada: Home Page</title> <meta name="dc.title" content="Government of Ontario, Canada: Home Page" />

For a bilingual website’s splash page with titles in both English and French:

<title>ONTERM Entry page/Page de garde d’ONTERM</title>
<meta name="dc.title" content="ONTERM Entry page" />
<meta name="dc.title" content="Page de garde d’ONTERM" />

For a non-HTML web resource with the formal title "Defining Programs and Services in the Ontario Public Service" and a commonly known informal title:

<meta name="dc.title" content="Defining Programs and Services in the Ontario Public Service" />

<meta name="dc.title.alternative" content="Service Definition Handbook" />

XML examples

For a slide show entitled "Knowledge Management in the OPS":

<dc:title>Knowledge Management in the OPS</dc:title> 

<dcterms:alternative>Generic KM Presentation</dcterms:alternative>

18. Type

HTML examples

For a news release where the term "News Release" was chosen from the "abc" controlled vocabulary:

<meta name="dc.type" scheme="abc" content="News Release" />

For a map posted on the web where the term "Map" was chosen from the "abc" controlled vocabulary:

<meta name="dc.type" scheme="abc" content="Map" />

XML examples

For a Memorandum of Understanding where a value is selected from the Government of Canada Type Scheme:

<dc:type xsi:type="gctype">agreement</dc:type> 

For a movie clip where a value is selected from the DCMI type scheme:

<dc:type xsi:type="dcterms:DCMIType">MovingImage</dc:type>

19. Update frequency

HTML examples

For a web resource that is to be updated every 3 months :

<meta name="go.updatefrequency"  content= “3 months” />

For a web resource that is to be updated as needed:

<meta name="go.updatefrequency" content= “As needed” />

XML examples

For a web resource that is to be updated every 3 months:

<meta name="go.updatefrequency" content= “Quarterly” />

For a web resource that is to be updated as needed:

<meta name="go.updatefrequency" content= “As needed” />

20. Version

HTML examples

For a web resource that is to be considered a draft version:

<meta name="go.version" content="draft version 1.3.0" />

For a web resource that is to be considered the final version:

<meta name="go.version" content="Final Version" />

For the second edition of version 3.0 of a web resource :

<meta name="go.version" content="Version 3.0, Second Edition" />

XML examples

For an information resource that is considered to be a draft version:

<go:version>Draft Version 1.0 </go:version>

For a resource considered to be the Final Version:

<go:version>Final Version </go:version>

For the second edition of version 2.0 of a document:

<go:version>Version 2.0, Second Edition</go:version>