Skip to content

Commit

Permalink
Merge pull request #7 from krylataya/master
Browse files Browse the repository at this point in the history
typos fixed
  • Loading branch information
monkeypants committed Feb 2, 2017
2 parents da4fee0 + 3c9efc4 commit ae417cd
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions docs/discovery_api.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Unresolved canonical input formatting issues:

## URN Encoding

The ADBC document specifies an URN-encoded business identifier, using the NID prefix and ISO 6523 identifer type schemes.
The ADBC document specifies an URN-encoded business identifier, using the NID prefix and ISO 6523 identifier type schemes.

```
Feature: URN encoded Identifiers
Expand All @@ -46,7 +46,7 @@ Scenario Outline: urn encoded ABN 33767197359 (LOWER CASE urn)

Unresolved issues:

* The document explains how NID URNs can encode various business identifier echemes, but is not explicit about which schemes are required. Do we need to support non-ABN identifiers?
* The document explains how NID URNs can encode various business identifier schemes, but is not explicit about which schemes are required. Do we need to support non-ABN identifiers?


## MD5 Hexdigest of URN encoded business identifier
Expand Down
4 changes: 2 additions & 2 deletions docs/management_api.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,11 +43,11 @@ Then I am able to update my DCP entry
```

The current DCL reference implementation:
* Uses an OIDC Identity Provider as a simulation of a trusted business identity provider that is loosely decoupled from the DCL and enables concent-based authorisation.
* Uses an OIDC Identity Provider as a simulation of a trusted business identity provider that is loosely decoupled from the DCL and enables consent-based authorisation.
* Assumes Australian Businesses (or providers acting on their behalf) will be able to nominate arbitrary DCPs, rather than assuming a authorised or certified list of DCPs.
* Assumes Australian Businesses will be able to directly control their own DCL records. It does not have a restrict access to a group of Accredited Access Points

This simplified Web User Interface (Web UI) has been specified to support integration testing, and possibly as a "minimum viable product" for the self-service user-story. It is not meant to imply that a DCL Management API in unessiscary, and the Simplified Web UI may be become redundant once a satisfactory Management API Specification has been agreed to.
This simplified Web User Interface (Web UI) has been specified to support integration testing, and possibly as a "minimum viable product" for the self-service user-story. It is not meant to imply that a DCL Management API is unnecessary, and the Simplified Web UI may be become redundant once a satisfactory Management API Specification has been agreed to.

The following Simplified Web UI SPEC is proposed as an interim measure
```
Expand Down

0 comments on commit ae417cd

Please sign in to comment.