IDN Catalogue Profile - Specification

1.4.1 Australian government-aligned metadata

This recommendation is to use metadata elements aligned with the National Data Commissioner's Guide on Metadata Attributes.

In addition to the elements listed in the minimum metadata section above:

1.4.2 Maximal Indigenous content representation

This recommendation is to use the same metadata elements as listed above for minimal metadata and the National Data Commissioner's Guide on Metadata Attributes but with specific sources for particular values.

In addition to the elements listed in the minimum metadata section above:

1.5.1 Turtle

Turtle is a text-based, reasonably human-readable syntax for RDF.

PREFIX dcat: <http://www.w3.org/ns/dcat#> PREFIX dcterms: <http://purl.org/dc/terms/> PREFIX prov: <http://www.w3.org/ns/prov#> PREFIX sdo: <https://schema.org/> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> <https://trove.nla.gov.au/work/10128420> a dcat:Resource ; dcterms:type <http://purl.org/dc/dcmitype/PhysicalObject> ; dcterms:title "Tjukinya" ; dcterms:description "Folktale: The little red hen retold in Pitjantjatjara" ; dcterms:creator <https://example.com/agent/123> ; dcterms:publisher <https://example.com/agent/123456> ; dcat:theme <https://data.idnau.org/pid/austlang/C6> ; prov:qualifiedAttribution [ prov:hadRole <https://linked.data.gov.au/def/data-roles/custodian> ; prov:agent <https://linked.data.gov.au/org/nla> ] ; dcterms:published "1980"^^xsd:gYear ; dcterms:theme <https://data.idnau.org/pid/austlang/C6> ; dcat:accessRights "Not for Inter-Library Loan" ; .

Note that the reference to the publisher, the Summer Institute of Linguistics, is by persistent identifier web address, https://example.com/agent/456, that resolves to more information about the Institute. This particular identifier is from the IDN Agents Database, so the IDN potentially knows more information about the Institute than just basic facts such as its name, for example whether it is an Indigenous-led organisation.

1.5.2 JSON-LD

JSON-LD is a convention for the use of JSON data that can represent RDF data. It is a modern syntax used by modern Web systems for data transfer.

This example JSON-LD has been converted from the Turtle data above and can be back-converted perfectly.

{ "@context": { "@vocab": "http://purl.org/dc/terms/", "accessRights": "http://www.w3.org/ns/dcat#accessRights", "theme": "http://www.w3.org/ns/dcat#theme", "Resource": "http://www.w3.org/ns/dcat#Resource", "year": "http://www.w3.org/2001/XMLSchema#gYear", "PhysicalObject": "http://purl.org/dc/dcmitype/PhysicalObject", "agent": "http://www.w3.org/ns/prov#agent", "hadRole": "http://www.w3.org/ns/prov#hadRole", "attribution": "http://www.w3.org/ns/prov#qualifiedAttribution", "austlang": "https://data.idnau.org/pid/austlang/C6", "data-roles": "https://linked.data.gov.au/def/data-roles/" }, "@graph": [ { "@id": "https://trove.nla.gov.au/work/10128420", "@type": "Resource", "type": { "@id": "http://purl.org/dc/dcmitype/PhysicalObject" }, "title": "Tjukinya", "description": "Folktale: The little red hen retold in Pitjantjatjara", "creator": { "@id": "https://example.com/agent/123" }, "publisher": { "@id": "https://example.com/agent/123456" }, "attribution": { "@id": "_:nb0e54b223f37485b8555e8d45b468bf9b1" } "published": { "@type": "year", "@value": "1980" }, "theme": { "@id": "https://data.idnau.org/pid/austlang/C6" }, "accessRights": "Not for Inter-Library Loan", }, { "@id": "_:nb0e54b223f37485b8555e8d45b468bf9b1", "agent": { "@id": "https://linked.data.gov.au/org/nla" }, "hadRole": { "@id": "data-roles:custodian" } } ] }

1.5.3 XML

XML is still commonly used as a format for metadata but care must be taken here: RDF/XML, a specific formulation of XML, must be used for XML data, not general-purpose XML.

The following RDF/XML has been generated from the Turtle example above.

<?xml version="1.0" encoding="utf-8"?> <rdf:RDF xmlns:dcat="http://www.w3.org/ns/dcat#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:prov="http://www.w3.org/ns/prov#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > <rdf:Description rdf:about="https://trove.nla.gov.au/work/10128420"> <rdf:type rdf:resource="http://www.w3.org/ns/dcat#Resource"/> <dcterms:type rdf:resource="http://purl.org/dc/dcmitype/PhysicalObject"/> <dcterms:title>Tjukinya</dcterms:title> <dcterms:description>Folktale: The little red hen retold in Pitjantjatjara</dcterms:description> <dcterms:creator rdf:resource="https://example.com/agent/123"/> <dcterms:publisher rdf:resource="https://example.com/agent/123456"/> <prov:qualifiedAttribution rdf:nodeID="n09d0151a1e6140cfb188576200eb9d69b1"/> <dcterms:published rdf:datatype="http://www.w3.org/2001/XMLSchema#gYear">1980</dcterms:published> <dcat:theme rdf:resource="https://data.idnau.org/pid/austlang/C6"/> <dcat:accessRights>Not for Inter-Library Loan</dcat:accessRights> </rdf:Description> <rdf:Description rdf:nodeID="n09d0151a1e6140cfb188576200eb9d69b1"> <prov:hadRole rdf:resource="https://linked.data.gov.au/def/data-roles/custodian"/> <prov:agent rdf:resource="https://linked.data.gov.au/org/nla"/> </rdf:Description> </rdf:RDF>

1.5.4 Other formats

All standard RDF formats may be used. As a guide, those able to be handled by the RDFLib code library are fine.

If you need to create RDF data for the first time, you can use the:

• IDN Metadata Creator tool

2.1.2 Catalogue

Req C1: Being a Resource, each Catalog instance MUST also adhere to the Resource Requirements R1, R2, R3 & R4.

Req C2: Each Catalog instance MUST contain at least one Resource indicated by the hasPart property.

Example: A Catalogue instance with minimum required metadata <https://doi.org/a-doi-for-the-catalogue> a dcat:Catalog ; dcterms:title "Catalogue X" ; dcterms:description "An example catalogue"@en ; dcterms:created "2022-07-21"^^xsd:date ; dcterms:modified "2022-07-25T20:15:21"^^xsd:dateTime ; prov:qualifiedAttribution [ a prov:Attribution; prov:agent <https://linked.data.gov.au/org/idn> ; # Indigenous Data Network's PID ex:hadRole :custodian ; ] , [ a prov:Attribution; prov:agent <https://orcid.org/0000-0002-8742-7730> ; # Nicholas Car's IRI ex:hadRole :pointOfContact ; ] ; dcterms:hasPart ex:some-resource-y , ex:some-resource-z , ... .

2.1.3 Resource

Req R1: Each Resource instance SHOULD indicate a persistent identifier to be used to gain access to its point-of-truth metadata. The PID SHOULD be used as the Dataset instance's IRI, if it is an HTTP/HTTPS IRI, or else it SHOULD be quoted as a literal value, indicated with the property dcterms:identifier of datatype xsd:token.

Req R2: Each Resource instance MUST provide basic Resource metadata so that exactly one of each of the following properties is required with range value as per Resource requirements: title, description, created & modified.

Req R3: Allowed Semantic Web date/time properties for created & modified properties are xsd:date, xsd:dateTime, xsd:dateTimeStamp, time:Interval

Req R4: Each Resource instance MUST NOT indicate Agent roles with direct DCAT properties (e.g. publisher) and MUST indicate them with the DCAT-recommended PROV qualified attribution pattern with each prov:Attribution indicated with the property prov:qualifiedAttribution.

Req R5: Each Resource instance, if it is not a Catalog instance MUST and if it is a Catalog instance MAY indicate that it is within at least one Catalog instance with an in-bound hasPart property from a Catalog instance.

Req R6: Each Resource instance MAY indicate that it is a specific type of resource by use of the dcterms:type property. Catalogued Dataset instances are equivalent to catalogued Resource instances of dcterms:type Dataset.

Example: A Resource instance with minimum required metadata <http://example.com/resource/x> a dcat:Resource ; dcterm:identifier "CAT::2-3-4::X"^^xsd:token ; # Dummy catalogue number dcterms:title "Resource X" ; dcterms:description "An example Resource"@en ; dcterms:created "2022-07-21"^^xsd:date ; dcterms:modified "2022-07-25T20:15:21"^^xsd:dateTime ; prov:qualifiedAttribution [ a prov:Attribution; prov:agent <http://example.com/org/clc> ; # Example Indigenous org PID ex:hadRole :custodian ; ] , [ a prov:Attribution; prov:agent <http://example.com/academic/person-x> ; # An academic ex:hadRole :author ; ] , [ a prov:Attribution; prov:agent <http://example.com/org/xyz-people> ; # An Indigenous group ex:hadRole :subjectAgent ; ] ; dcterms:type ex:map ; # An example specialised resource - a map - from some vocabularty of types . <https://doi.org/a-doi-for-a-catalogue> # a catalogue indicating this Resource is a part of it dcterms:hasPart <http://example.com/resource/x> ; .

2.1.3 Dataset

There are no structural requirements specifically for Dataset instances: the requirements for Resource also apply to Dataset.

Note that there are values requirements for Dataset instnaces, as per the next section.

2.1.1 Attribution

Req A1: Each Attribution instance MUST indicate an Agent instance with the property prov:agent and a role for that Agent, as a skos:Concept, in relation to the attributing entity, with the hadRole property.

Example: A Resource with a qualified Attribution <http://example.com/resource/x> a dcat:Resource ; ... prov:qualifiedAttribution [ a prov:Attribution; prov:agent <http://example.com/resource/central-lands-council> ; dcat:hadRole :custodian ; ] ; ... .

2.1.5 Agent

Agents are the Organisations & People that have Roles in relation to Catalogues and Resources.

Req AG1: Each Agent instance MUST be either an sdo:Organization or a sdo:Person instance.

Req AG2: Each Agent instance MUST be described with at least the sdo:name property and, if an sdo:Organization, also an sdo:url property with a xsd:anyURI value or, if a sdo:Person, an sdo:email property with a xsd:anyURI value.

Req AG3: Each Agent instance SHOULD be described with a sdo:description property and, if the Agent has them, identifiers for it should be indicated with sdo:identifier with xsd:anyURI or xsd:token values.

Req AG4: Each Agent MAY relate other information using schema.org properties, for example sdo:affiliation to link a sdo:Person to an sdo:Organization.

Example: An Organization with an example Australian Business Number identifer and a Person affiliated with it <https://kurrawong.ai> a sdo:Organization ; sdo:identifier "31 353 542 036"^^ex:ABN ; sdo:name "KurrawongAI" ; sdo:description "KurrawongAI is a small, Artificial Intelligence, company in Australia specialising in Knowledge Graphs." ; sdo:url "https://kurrawong.ai"^^xsd:anyURI ; . <https://orcid.org/0000-0002-8742-7730> a sdo:Person ; sdo:name "Nicholas J. Car"@en ; sdo:email "nick@kurrawong.ai"^^xsd:anyURI ; sdo:affiliation <https://kurrawong.ai> ; .

2.1.5 Concept

This profile is a profile of Vocabulary Publications Profile, VocPub, among other specifications. VocPub sets requirements for Concept and ConceptScheme instances.

See the VocPub Concept requirements listed in its Specification:

• VocPub Specification: Concept

Example: A Concept with basic VocPub requirements met <http://example.com/concept/x> a skos:Concept ; rdfs:isDefinedBy <http://example.com/concept-scheme/y> ; # Indicating the vocabulary that defines this term skos:prefLabel "Concept X"@en ; # The Concepts preferred label skos:altLabel "Xxx"@en ; # A synonym/alias skos:definition "An example Concept"@en ; # The Concept's definition skos:narrower <http://example.com/concept/x.1> ; .

2.1.6 ConceptScheme

This profile is a profile of Vocabulary Publications Profile, VocPub, among other specifications. VocPub sets requirements for Concept and ConceptScheme instances.

See the VocPub ConceptScheme requirements listed in its Specification's Vocabulary section:

• VocPub Specification: Vocabulary

B.4.1 Introduction

This Local Context model is a small ontology providing just a few classes and properties to indicate how to attach LC labels to objects catalogued according to this profile.

The machine-readable version of this model is available at:

• https://data.idnau.org/pid/vocab/lc-labels

The prefix lc: is used in this section for the namespace of this model: https://data.idnau.org/pid/vocab/lc-labels/.

Figure B.4.1 overviews the model.

Figure B.4.1: Overview of elements of the Local Context Model.

This model requires that a LocalContextLabel, which is a specialised skos:Concept, is assigned to a catalogued dcat:Resource via an intermediate node of type QualifiedLocalContext. This use of the "Qualified Relations" graph modelling pattern allows for the nature of the Resource/LocalContextLabel relationship to be defined.

B.4.2 Definitions

B.4.3 LocalContextLabel instances

LocalContextLabel instances for all defined TK & BC labels are given in two vocabularies:

1. BC Labels Vocabulary
2. TK Labels Vocabulary

The vocabularies above, while they have been created by the IDN, are not available publicly.

An example of RDF data for one of these labels is:

PREFIX tk: <https://data.idnau.org/pid/vocab/tk-labels/> tk:women-restricted a skos:Concept , lc:TKLabel ; dcterms:identifier "women-restricted"^^xsd:token ; dcterms:source "https://localcontexts.org/label/tk-women-restricted/"^^xsd:anyURI ; rdfs:isDefinedBy cs: ; skos:definition "This Label should be used when you want to let external users know that the material circulating freely is actually of a highly restricted nature. This is a Women’s Highly Restricted Label and indicates that there are restrictions of access and use based on customary law. This Label can be used to help external users recognize that with this material there are very specific protocols and conditions of use. This Label is designed to recognize that some knowledge is gendered, and that certain knowledge expressions can only be shared among specific members of the community. Only authorized [and/or initiated] women within the community should be using this material."@en ; skos:inScheme cs: ; skos:notation "TK WR" ; skos:prefLabel "Women Restricted"@en ; .

B.4.4 Examples of a Resource with LC labels

Example: A Dataset that does have a label applied to it but requires one <https://www.atsida.edu.au/archive/datasets/au.edu.anu.ada.ddi.20002-aus> a dcat:Dataset; dcterms:title "Annual Aboriginal Census,1921-1944 - Australia"@en ; ... dcat:theme [ a lc:QualifiedLocalContext ; dcterms:type tk:culturally-sensitive ; lc:requirement "This dataset contains information collected in ways no longer thought to be best practice. The data may, if used unwarily, put Indigenous people in an un-due negative light."@en ; ] ; ... .

Example: A Dataset that does have a label applied to it but requires one <http://dx.doi.org/10.26193/V93KUP> a dcat:Dataset; dcterms:title "Aboriginal radio broadcasting in Alice Springs, 1981"@en ; ... dcat:theme [ a lc:QualifiedLocalContext ; dcterms:type tk:multiple-communities ; rdf:value "Responsibility and ownership over this material is spread across several distinct communities. Use will be dependent upon discussion and negotiation with the multiple communities named herein Central Lands Council, Waltja Tjutangku Palyapayi Aboriginal Corporation, Akeyulerre Healing Centre. Decisions about use will need to be decided collectively. As an external user of this material you are asked to recognize and respect cultural protocols in relation to the use of this material and clear your intended use with the relevant communities."@en ; ] ; ... .