refactoring after renaming UBL-* to SYN v1 and v2

ausdigital · Jan 29, 2017 · fb472f1 · fb472f1
1 parent d993ea8
commit fb472f1
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 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/dbc-specs/)) 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/ausdigital-dcl/blob/master/docs/Digital_Capability_Locator_Implementation_Guide_v1.0.pdf)) 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,7 +42,7 @@ 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/dbc-specs/)), which provides background to the [AusDigital](http://ausdigital.org) community process.
+ * ADBC DCL Implementation Guide (v1.0, available [here](https://github.com/ausdigital/ausdigital-dcl/blob/master/docs/Digital_Capability_Locator_Implementation_Guide_v1.0.pdf)), 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/).

diff --git a/docs/management_api.md b/docs/management_api.md
@@ -23,7 +23,7 @@ The current AusDigital specification is in a raw status (not yet draft). Please
 
 ## ADBC Proposal
 
-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
+Section 8 of the ADBC DCL Implementation Guide (v1.0, available [here](https://github.com/ausdigital/ausdigital-dcl/blob/master/docs/Digital_Capability_Locator_Implementation_Guide_v1.0.pdf)) 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.