Skip to content

Commit

Permalink
examples
Browse files Browse the repository at this point in the history
  • Loading branch information
@nicholascar
nicholascar committed Aug 14, 2024
1 parent 81a2798 commit 24243ea
Showing 1 changed file with 16 additions and 6 deletions.
22 changes: 16 additions & 6 deletions docs/pids.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -123,12 +123,12 @@ To create an IRI, we need to consider the Case of object the IRI is for, as per

#### Patterns per Case

| Case | Pattern | Elements |
|---------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1. **high-level definitional object** | `https://linked.data.gov.au/def/{ID}` | `{ID}` - may be anything acceptable to the [Australian Government Linked Data Working Group](https://linked.data.gov.au) which means be in accordance with their [Guidelines](https://www.linked.data.gov.au/guidelines). See [Registration](pids.md#registration) below. |
| 2. **low-level definitional object** | `https://linked.data.gov.au/def/{ID}/{LOW-LEVEL-ID}` | `{ID}` - as per the requirements above <br />`{LOW-LEVEL-ID}` - distinct within the scope of the high-level object that contains this low-level object, e.g. unique Concept IDs within a Vocabulary, starting with a upper-letter if for a Class or Concept, starting with a lower-case letter if for a Predicate |
| 3. **high-level data object** | `https://linked.data.gov.au/dataset/{ID}` | As per Case 1 |
| 4. **low-level definitional object** | `https://linked.data.gov.au/dataset/{ID}/{LOW-LEVEL-ID}` | As per Case 2 |
| Case | Pattern | Elements |
|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1. **high-level definitional object** | `https://linked.data.gov.au/def/{ID}` | `{ID}` - may be anything acceptable to the [Australian Government Linked Data Working Group](https://linked.data.gov.au) which means be in accordance with their [Guidelines](https://www.linked.data.gov.au/guidelines). See [Registration](pids.md#registration) below. |
| 2. **low-level definitional object** | `https://linked.data.gov.au/def/{ID}/{LOW-LEVEL-ID}` | `{ID}` - as per the requirements above <br />`{LOW-LEVEL-ID}` - distinct within scope of containing high-level object, starting upper-letter if a Class, starting lower-case letter if a Predicate |
| 3. **high-level data object** | `https://linked.data.gov.au/dataset/{ID}` | As per Case 1 |
| 4. **low-level definitional object** | `https://linked.data.gov.au/dataset/{ID}/{LOW-LEVEL-ID}` or<br />`https://linked.data.gov.au/dataset/{ID}/{CLASS-SIGNIFIER}/{LOW-LEVEL-ID}` | As per Case 2 or use of an additional path element, `{CLASS-SIGNIFIER}`, to indicate the class of object as well as its individual ID. |

#### Classes per Case

Expand All @@ -142,6 +142,16 @@ Specific classes of object per Case as listed above are:
| 4. **low-level definitional object** | everything else not listed in Cases 1 - 3 |


#### Examples

| Case | Examples |
|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1. **high-level definitional object** | Ontology - `https://linked.data.gov.au/def/bore` - _Bore Model_<br />ConceptScheme - `https://linked.data.gov.au/def/borehole-drilling-method-western-australia` - _Borehole Drilling Method_ vocabulary |
| 2. **low-level definitional object** | Class - `https://linked.data.gov.au/def/bore/Bore` - _Bore_ class in Bore Model<br />Property - `https://linked.data.gov.au/def/bore/hadDrillingMethod` - _had drilling method_ property in Bore Model<br />Concept - `https://linked.data.gov.au/def/borehole-drilling-method-western-australia/non-rotary` - _non-rotary drilling_ concept in _Borehole Drilling Method_ vocabulary<br />NodeShape - _coming soon_<br />PropertyShape - _coming soon_ |
| 3. **high-level data object** | Dataset - _coming soon_<br />DataCatalog - _coming soon_ |
| 4. **low-level definitional object** | _coming soon_ |
| x. **Organisations** | `https://linked.data.gov.au/org/gswa` - GSWA within the AGLDWG Org Register |

## Agents

Agents - Organisations and People - have a couple of special considerations. When they are referred to in data, they would be considered instances of a _low-level definitional object_ however two particular sources of existing IRIs for them _SHOULD_ be considered:
Expand Down

0 comments on commit 24243ea

Please sign in to comment.