Skip to content

Commit 076b3b1

Browse files
Fixed feedback by xdxxxdx
1 parent c8f0b58 commit 076b3b1

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

01-tree-specification.bs

+4-4
Original file line numberDiff line numberDiff line change
@@ -137,16 +137,16 @@ Note: Having an identifier for the collection has become mandatory: without it y
137137
# The member extraction algorithm # {#member-extraction-algorithm}
138138

139139
The member extraction algorithm allows a data publisher to define their members in different ways:
140-
1. As in the examples above: all quads with the object of the `tree:member` quads as a subject (and recursively the quads of their blank nodes) are by default included (see also [[!CBD]]), except when they would explicitely not be included in case 3, when the shape would be closed.
140+
1. As in the examples above: all quads with the object of the `tree:member` quads as a subject (and recursively the quads of their blank nodes) are by default included (see also [[!CBD]]), except when they would explicitly not be included in case 3, when the shape would be closed.
141141
2. Out of band / in band:
142142
- when no quads of a member have been found, the member will be dereferenced. This allows to publish the member on a separate page.
143143
- part of the member can be maintained elsewhere when a shape is defined (see 3)
144144
3. By defining a more complex shape with `tree:shape`, also nested entities can be included in the member
145145
4. By putting the triples in a named graph of the object of `tree:member`, all these triples will be matched.
146146

147147
Depending on the goals of the client, it MAY implement the member extraction algorithm to fetch all triples about the entity as intended by the server.
148-
The method used withun TREE is combination of Concise Bounded Descriptions [[!CBD]], named graphs and the topology of a shape (deducted from the `tree:shape`).
149-
The full algorithm is specificied in the [shape topologies](https://w3id.org/tree/specification/shape-topologies) report.
148+
The method used within TREE is combination of Concise Bounded Descriptions [[!CBD]], named graphs and the topology of a shape (deducted from the `tree:shape`).
149+
The full algorithm is specified in the [shape topologies](https://w3id.org/tree/specification/shape-topologies) report.
150150

151151
# Traversing the search tree # {#traversing}
152152

@@ -265,7 +265,7 @@ The behaviour of the search form fully depends on the specific property, for whi
265265

266266
Three properties allow to specify a geospatial XYZ tiles template (also known as slippy maps).
267267
1. `tree:longitudeTile` describes the X value
268-
2. `tree:latitudeTile` descrbes the Y value
268+
2. `tree:latitudeTile` describes the Y value
269269
3. `tree:zoom` describes the zoom level
270270

271271
All properties expect positive integers.

03-discovery-specification.bs

+1-1
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Issue: Will we document the precise algorithm to use? Should we extend shapes wi
5353
## Selecting a collection via a catalog ## {#dcat-catalog}
5454

5555
A DCAT Catalog is an overview of datasets, data services and distributions.
56-
As TREE clients first need to select a dataset, and then a search tree to use, it aligns wll with how DCAT-AP works.
56+
As TREE clients first need to select a dataset, and then a search tree to use, it aligns with how DCAT-AP works.
5757
DCAT discovery extends upon the previous section in which a collection or dataset can be selected based on the `tree:shape` property.
5858

5959
For now, we will assume the DCAT information is available in subject pages.

0 commit comments

Comments
 (0)