many updates

document/00-master.adoc

@@ -17,8 +17,12 @@ include::07-good-practices.adoc[]
 
 include::08-governance-framework.adoc[]
 
+include::09-reqs-recs.adoc[]
+
 :sectnums!:
 
-include::50-annex-a-identifiers.adoc[]
+include::50-annex-a-extended-examples.adoc[]
+
+include::51-annex-b-identifiers.adoc[]
 
 include::99-bibliography.adoc[]

document/03-preamble.adoc

@@ -88,6 +88,45 @@ For process and information to be conformant with this standard, the imperatives
 
 Address information created following processes outlined in this standard _MUST_ conform to the <<ADDR2024, ICSM Address Model>> with conformance to it tested as per it's https://linked.data.gov.au/def/addr#AnnexB[Annex B: Validation] section.
 
+=== Namespaces
+
+Namespaces, in this document's context, are managed <<IRI, IRIs>> which allow further IRIs to be created within their scope. Namespaces are allocated to macro data objects and provide IRIs for all the micro data objects within that object.
+
+For example, the IRI for the <<ADDR2024, Address Model>> is `+https://linked.data.gov.au/def/addr+` and the namespace of `+https://linked.data.gov.au/def/addr/+` (the Address Model's IRI + `/`) allows for IRIs to be created for elements within the model such as one for the `AddressableObject` class which is `+https://linked.data.gov.au/def/addr/AddressableObject+`.
+
+When used in some forms of data and human-readable text, IRIs can either be written in full or in a shortened form using prefixes for known namespace. For example, the `Addresable Object` mentioned above can be written in full like this:
+
+`+https://linked.data.gov.au/def/addr/AddressableObject+`
+
+or in prefixed form with the prefix `addr` for the namespace `+https://linked.data.gov.au/def/addr/+` like this:
+
+`addr:AddressableObject`
+
+The prefixed namespaces used in this document are:
+
+[width=100%, frame=none, grid=none, cols="1,5,4"]
+|===
+|Prefix | Namespace | Description
+
+| `*addr*` | `*+https://linked.data.gov.au/def/addr/+*` | <<ADDR2024, ICSM's  Address Model>>
+| `*addrcm*` | `*+https://linked.data.gov.au/def/addrcm/+*` | *This Document*
+| `addreq` | `+https://linked.data.gov.au/def/addrcm-req/+` | https://linked.data.gov.au/def/addrcm-req[Address Creation & Maintenance Requirements Vocabulary]
+| `als` | `+https://linked.data.gov.au/def/address-lifecycle-stage-type/+` | https://linked.data.gov.au/def/lifecycle-stage-types[Address Lifecycle Stage Types vocabulary]
+| `apt` | `+https://linked.data.gov.au/def/address-part-type/+` | https://linked.data.gov.au/def/addr-part-types[Address Part Types vocabulary]
+| `asgsed3` | `+https://linked.data.gov.au/dataset/asgsed3/+` | https://linked.data.gov.au/dataset/asgsed3[Australian Statistical Geographies Standard Dataset, Release 3]
+| `cn` | `+https://linked.data.gov.au/def/cn/+` | https://linked.data.gov.au/def/cn[Compound Naming Model]
+| `ex` | `+http://example.com/+` | Generic examples
+| `geo` | `+http://www.opengis.net/ont/geosparql#+` | https://docs.ogc.org/is/22-047r1/22-047r1.html[OGC GeoSPARQL]
+| `gt` | `+http://www.opengis.net/ont/geocode-types/+` | https://linked.data.gov.au/def/geocode-types[Geocode types vocabulary]
+| `ls` | `+https://linked.data.gov.au/def/lifecycle/+` | https://linked.data.gov.au/def/lifecycle[Lifecycle Model]
+| `owl` | `+http://www.w3.org/2002/07/owl#+` | https://www.w3.org/TR/owl2-overview/[Web Ontology Language ontology]
+| `rdf` | `+http://www.w3.org/1999/02/22-rdf-syntax-ns#+` | https://www.w3.org/TR/rdf-concepts/[The RDF Concepts Vocabulary]
+| `rdfs` | `+http://www.w3.org/2000/01/rdf-schema#+` | https://www.w3.org/TR/rdf12-schema/[RDF Schema ontology]
+| `sdo` | `+https://schema.org/+` | https://schema.org[schema.org model]
+| `skos` | `+http://www.w3.org/2004/02/skos/core#+` | https://www.w3.org/TR/skos-reference/[Simple Knowledge Organization System (SKOS) ontology]
+| `time` | `+http://www.w3.org/2006/time#+` | https://www.w3.org/TR/owl-time/[Time Ontology in OWL]
+| `xsd` | `+http://www.w3.org/2001/XMLSchema#+` | https://www.w3.org/TR/xmlschema-2/[XML Schema Definitions ontology]
+|===
 
 ////
 === Notation

document/04-introduction.adoc

@@ -1,3 +1,9 @@
 == Introduction
 
-This is a placeholder
+This is a placeholder
+
+* abstract
+* purpose
+* history
+* big picture
+* doc structure

document/08-governance-framework-old.adoc

@@ -0,0 +1,159 @@
+== Governance Framework
+
+=== General
+
+==== Strategy
+
+*Requirement 16* `addrcm-req:strategy`
+
+A governance framework shall be guided by a strategy for assigning addresses to objects. The strategy shall be based on policies and guidelines.
+
+TBC
+
+==== Policies
+
+*Requirement 17* `addrcm-req:policies`
+
+A governance framework shall exercise authority and control over address assignment and maintenance through policies with well defined decision-making structures and procedures.
+
+TBC
+
+*Recommendation 13* `addrcm-req:policiesSupportObjectivesAndContext`
+
+The policies should support the objectives and context.
+
+TBC
+
+==== Good Practice
+
+*Requirement 18* `addrcm-req:goodPractice`
+
+A governance framework shall specify the good practice according to which addresses shall be assigned and maintained (see clause 8).
+
+TBC
+
+=== Addressing Stakeholders
+
+==== Identification
+
+*Requirement 19* `addrcm-req:identification`
+
+A governance framework shall identify the addressing stakeholders involved in the processes and decision-making related to assignment and maintenance of addresses.
+
+TBC
+
+==== Responsibilities
+
+*Requirement 20* `addrcm-req:responsibilities`
+
+A governance framework shall assign at least one responsibility to each stakeholder in the governance framework, and they shall be accountable for their responsibilities.
+
+TBC
+
+==== Mandates
+
+*Requirement 21* `addrcm-req:mandates`
+
+Assignment of responsibilities to stakeholders shall consider legal and other mandates. Responsibilities are assigned to each stakeholder in the governance framework based on the extent of the mandate of the respective stakeholders.
+
+TBC
+
+==== Resourcing
+
+*Requirement 22* `addrcm-req:resourcing`
+
+Stakeholders shall take responsibility for how they are funded, resourced and organized to fulfil their responsibilities in the governance framework.
+
+TBC
+
+==== Sustainability
+
+*Requirement 23* `addrcm-req:sustainability`
+
+Funding and resourcing of stakeholders in a governance framework shall be sustainable, i.e., ongoing and able to be maintained in the long run.
+
+TBC
+
+=== Processes
+
+==== Specification
+
+*Requirement 24* `addrcm-req:specification`
+
+A governance framework shall specify and coordinate the processes for assigning and maintaining addresses, as specified in 8.3.1, and if address data is maintained, it shall specify and coordinate the required processes related to address data, specified in 8.3.2. Each process comprises a series of tasks towards achieving a specified goal.
+
+TBC
+
+==== Tasks
+
+*Requirement 25* `addrcm-req:tasks`
+
+A governance framework shall assign at least one stakeholder to each task in a process.
+
+TBC
+
+==== Addressing Processes
+
+===== Initiation Process
+
+*Requirement 26* `addrcm-req:initiationProcess`
+
+A governance framework shall specify and coordinate a process for initiating the assignment or maintenance of an address.
+
+TBC
+
+*Recommendation 14* `addrcm-req:consultationProcess`
+
+A governance framework should specify and coordinate a process for consultation when new address component values are assigned or changed due to maintenance.
+
+TBC
+
+===== Purpose Values Process
+
+*Requirement 27* `addrcm-req:proposeValuesProcess`
+
+A governance framework shall specify and coordinate a process for proposing new values or changes to address components values.
+
+TBC
+
+===== Approval Process
+
+*Requirement 28* `addrcm-req:approvalProcess`
+
+A governance framework shall specify and coordinate a process for approving or rejecting the proposed new address assignment or changes to an address due to maintenance.
+
+TBC
+
+===== Announcement Process
+
+*Requirement 29* `addrcm-req:announcementProcess`
+
+A governance framework shall specify and coordinate a process for the announcement of a newly assigned address or changes to an address due to maintenance.
+
+TBC
+
+===== Communication Process
+
+*Requirement 30* `addrcm-req:communicationProcess`
+
+A governance framework shall specify a process for communicating addresses in the physical world, following approval of assignment or maintenance of an address.
+
+TBC
+
+==== Address Data Processes
+
+===== Update Process
+
+*Requirement 31* `addrcm-req:updateProcess`
+
+A governance framework shall specify and coordinate a process for updating the authoritative dataset after approval of assignment or maintenance of an address.
+
+TBC
+
+===== Distribution Process
+
+*Requirement 32* `addrcm-req:distributionProcess`
+
+A governance framework shall specify and coordinate a process for making address data available after an update to the authoritative dataset.
+
+TBC

document/08-governance-framework.adoc

@@ -1,3 +1,2 @@
 == Governance Framework
 
-_For assigning and maintaining addresses_