Skip to content

Commit b4be21e

Browse files
committed
Quick spell check
1 parent 1a9c5cf commit b4be21e

5 files changed

+16
-16
lines changed

datasets-catalog.apib

+4-4
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Use the **showShared** header parameter to include the public datasets.
1212
+ Accept: (required, mimetype) -
1313
```application/ld+json``` or ```application/rdf+xml```
1414
15-
### List users's datasets [GET]
15+
### List user's datasets [GET]
1616
1717
+ Request
1818
+ Headers
@@ -61,7 +61,7 @@ Use the **showShared** header parameter to include the public datasets.
6161
+ Accept: (required, mimetype) -
6262
```application/ld+json``` or ```application/rdf+xml```
6363
64-
### Search users's datasets [GET]
64+
### Search user's datasets [GET]
6565
+ Request
6666
+ Headers
6767
Accept: application/ld+json
@@ -104,7 +104,7 @@ Use the **showShared** header parameter to include the public datasets.
104104
105105
If the description contains no `@id`, the system will generate one from the title.
106106
107-
A successfull creation returns the URI of the new dataset.
107+
A successful creation returns the URI of the new dataset.
108108
109109
+ Parameters
110110
+ Content%2DType: (required, mimetype) -
@@ -208,7 +208,7 @@ When deleting a dataset, the system will also delete the attached distributions.
208208
209209
### Create Distribution [POST]
210210
211-
A successfull creation returns the URI of the new dataset.
211+
A successful creation returns the URI of the new dataset.
212212
213213
**Attachments**
214214

model-reference.apib

+1-1
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The Datagraft API supports [RDF/XML](https://en.wikipedia.org/wiki/RDF/XML) and
6161

6262
### JSON-LD
6363

64-
JSON-LD, or JavaScript Object Notation for Linked Data is the recommended way to consume and provide data. You can use the same software as traditional JSON. The `@context`, `@type` and `@id` properties are JSON-LD specific.
64+
JSON-LD or JavaScript Object Notation for Linked Data is the recommended way to consume and provide data. You can use the same software as traditional JSON. The `@context`, `@type` and `@id` properties are JSON-LD specific.
6565

6666
**Example:**
6767

rdf-repositories.apib

+3-3
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@
33

44
## OpenRDF Sesame [/]
55

6-
The RDF repositories API is accessible at the address ```https://rdf.datagraft.net/```.
6+
The RDF repositories API are accessible at the address ```https://rdf.datagraft.net/```.
77

8-
It exposes the [OpenRDF Sesame API](http://rdf4j.org/sesame/2.7/docs/system.docbook?view).
8+
This endpoint exposes the [OpenRDF Sesame API](http://rdf4j.org/sesame/2.7/docs/system.docbook?view).
99

1010
**However the authentication is still required.** Using the Authorization header as defined in the beginning of this document.
1111

@@ -15,7 +15,7 @@ It exposes the [OpenRDF Sesame API](http://rdf4j.org/sesame/2.7/docs/system.docb
1515

1616
Use `/catalog/distributions/repository_async` to provision the repository asynchronously.
1717

18-
This service returns a repository url.
18+
This service returns a repository URL.
1919

2020
+ Parameters
2121
+ distrib%2Did: (required, URI) -

security-and-authentication.apib

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Group Security and authentication
22

3-
The Datagraft API is restricted to authentified application, using an access key and a secret. You can manage your access keys and secrets using the [Datagraft API key manager](http://datagraft.net/pages/keymanager/index.jsp).
3+
The Datagraft API is restricted to authenticated application, using an access key and a secret. You can manage your access keys and secrets using the [Datagraft API key manager](http://datagraft.net/pages/keymanager/index.jsp).
44

55

66
#### HTTPS
@@ -10,7 +10,7 @@ The API is only accessible through HTTPS.
1010

1111
#### Authentication
1212

13-
The authentication is done using HTTP Basic authentication, and therefore the HTTP authorization header field. It consists of the text 'Basic ' concatened with the base64 encoding of the API key and the API secret separated by a colon.
13+
The authentication is done using HTTP Basic authentication, and therefore the HTTP authorization header field. It consists of the text 'Basic ' concatenated with the base64 encoding of the API key and the API secret separated by a colon.
1414

1515
Example in JavaScript:
1616
```javascript

transformations-catalog.apib

+6-6
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Use the **showShared** header parameter to include the public transformations.
1212
+ Accept: (required, mimetype) -
1313
```application/ld+json``` or ```application/rdf+xml```
1414
15-
### List users's transformations [GET]
15+
### List user's transformations [GET]
1616
1717
+ Request
1818
+ Headers
@@ -61,7 +61,7 @@ Use the **showShared** header parameter to include the public transformations.
6161
+ Accept: (required, mimetype) -
6262
```application/ld+json``` or ```application/rdf+xml```
6363
64-
### Search users's transformations [GET]
64+
### Search user's transformations [GET]
6565
+ Request
6666
+ Headers
6767
Accept: application/ld+json
@@ -102,19 +102,19 @@ Use the **showShared** header parameter to include the public transformations.
102102
103103
### Create Transformation [POST]
104104
105-
A successfull creation returns the URI of the new transformation.
105+
A successful creation returns the URI of the new transformation.
106106
107107
If the description contains no `@id`, the system will generate one from the title.
108108
109-
Note: only new transformations are created with this method. Any subsequent calls with the same data generates an error response.
109+
Note: only new transformations are created with this method. Any subsequent calls with the same data generate an error response.
110110
111111
**Attachments**
112112
113113
**meta:** Transformation metadata as RDF or JSON-LD.
114114
115115
Use `Content-Type` to determine the metadata-format.
116116
117-
If the metadata doesn't contain a distirbution id, the system will generate one.
117+
If the metadata doesn't contain a distribution id, the system will generate one.
118118
119119
**tr-clojure:** The code of the transformation as Grafter Clojure.
120120
@@ -195,7 +195,7 @@ Note: The complete transformation metadata should be included. It is not merged
195195
196196
**tr-clojure:** Optional code of the transformation as Grafter Clojure.
197197
198-
meta and tr-clojure cand be managed separately.
198+
meta and tr-clojure can be managed separately.
199199
200200
+ Parameters
201201
+ Content%2DType: (required, mimetype) -

0 commit comments

Comments
 (0)