fix links - ausdigital.github.io/issues/19

ausdigital · Jan 16, 2017 · fe770df · fe770df
1 parent bfd5ee6
commit fe770df
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/docs/discovery_api.md b/docs/discovery_api.md
@@ -1,6 +1,6 @@
 # Discovery API
 
-Section 7 of the ADBC DCL Implementation Guide (v1.0 available [here](https://github.com/ausdigital/adbc/)) specifies DNS NAPTR records as a DCL query API.
+Section 7 of the ADBC DCL Implementation Guide (v1.0 available [here](https://github.com/ausdigital/dbc-specs/)) specifies DNS NAPTR records as a DCL query API.
 
 This requires client to create an appropriately formed query, which is then sent through the DNS system where it is matched with a NAPTR record (maintained by the DCL service)
 

diff --git a/docs/index.md b/docs/index.md
@@ -42,8 +42,8 @@ The DCL-SPEC defines the interfaces and protocols a central address book, publis
 
 # Related Material
 
- * ADBC DCL Implementation Guide (v1.0, available [here](https://github.com/ausdigital/adbc/)), which provides background to the [AusDigital](http://ausdigital.org) community process.
- * [GitHub issues](https://github.com/ausdigital/capability-locator/issues/) for collaborating on the development of the DCL-SPEC
+ * ADBC DCL Implementation Guide (v1.0, available [here](https://github.com/ausdigital/dbc-specs/)), which provides background to the [AusDigital](http://ausdigital.org) community process.
+ * [GitHub issues](https://github.com/ausdigital/ausdigital-dcl/issues/) for collaborating on the development of the DCL-SPEC
  * A reference [DCL service](https://dcl.testpoint.io/) (for testing and development purposes)
  * Free, Open-Source Software [DCL implementation](https://github.com/test-point/dcl.testpoint.io/).
  * An automated [DCL test suite](https://github.com/test-point/test-capability-locator/).
diff --git a/docs/management_api.md b/docs/management_api.md
@@ -18,12 +18,12 @@ I need the ability to update my customer's SMP specification in the DCL
 So that I can configure the DCL on their behalf
 ```
 
-The current AusDigital specification is in a raw status (not yet draft). Please contribute to the discussion at the [DCL issue system](https://github.com/ausdigital/capability-locator/issues/).
+The current AusDigital specification is in a raw status (not yet draft). Please contribute to the discussion at the [DCL issue system](https://github.com/ausdigital/ausdigital-dcl/issues/).
 
 
 ## ADBC Proposal
 
-Section 8 of the ADBC DCL Implementation Guide (v1.0, available [here](https://github.org/ausdigital/adbc/)) specifies the Management API "used to register a relationship between a Participant
+Section 8 of the ADBC DCL Implementation Guide (v1.0, available [here](https://github.org/ausdigital/dbc-specs/)) specifies the Management API "used to register a relationship between a Participant
 Identifier and a Digital Capability Publisher".
 
 This specifies HTTPS interfaces with client certificate authentication and json or XML payloads. The CREATE and DELETE interfaces are mandatory, and the UPDATE interface is optional. More work is required to resolve how these client certificates might be issued and managed. In it's current form, there appear to be practical limits on supportability of the Self Service user-story.

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -1,5 +1,5 @@
 site_name: Digital Capability Locator SPEC
-repo_url: https://github.com/ausdigital/capability-locator
+repo_url: https://github.com/ausdigital/ausdigital-dcl
 pages:
     - 'Introduction': 'index.md'
     - 'Discovery API': 'discovery_api.md'