diff --git a/api-rest.md b/api-rest.md
index e32502e..1918538 100644
--- a/api-rest.md
+++ b/api-rest.md
@@ -58,92 +58,6 @@ HTTP/1.1 200 OK
     <http://www.w3.org/ns/posix/stat#size> "780" .
 ```
 
-#### Globbing (inlining on GET)
-
-**Note: this feature is _at risk_ of being
-[changed](https://github.com/solid/solid-spec/pull/148)
-or [removed](https://github.com/solid/solid-spec/pull/151).
-Please join the discussion.
-Code depending on this will still work for now.**
-
-We have found that in some cases, using the existing LDP features was not
-enough. For instance, to optimize certain applications we needed to aggregate
-all RDF resources from a container and retrieve them with a single GET
-operation. We implemented this feature on the servers and decided to call it
-"globbing". Similar to [UNIX shell
-glob](https://en.wikipedia.org/wiki/Glob_(programming)), doing a GET on any URI
-which ends with a `*` will return an aggregate view of all the resources that
-match the indicated pattern.
-
-For example, let's assume that `/data/res1` and `/data/res2` are two resources
-containing one triple each, which defines their type as follows:
-
-For *res1*:
-
-```ttl
-<> a <https://example.org/ns/type#One> .
-```
-
-For *res2*:
-
-```ttl
-<> a <https://example.org/ns/type#Two> .
-```
-
-If one would like to fetch all resources of a container beginning with `res`
-(e.g. `/data/res1`, `/data/res2`) in one request, they could do a GET on
-`/data/res*` as follows.
-
-REQUEST:
-
-```http
-GET /data/res* HTTP/1.1
-Host: example.org
-```
-
-RESPONSE:
-
-```http
-HTTP/1.1 200 OK
-```
-```ttl
-<res1>
-    a <https://example.org/ns/type#One> .
-
-<res2>
-    a <https://example.org/ns/type#Two> .
-```
-
-Alternatively, one could ask the server to inline *all* resources of a
-container, which includes the triples corresponding to the container itself:
-
-REQUEST:
-
-```http
-GET /data/* HTTP/1.1
-Host: example.org
-```
-
-RESPONSE:
-
-```http
-HTTP/1.1 200 OK
-```
-```ttl
-<>
-    a <http://www.w3.org/ns/ldp#BasicContainer> ;
-    <http://www.w3.org/ns/ldp#contains> <res1>, <res2> .
-
-<res1>
-    a <https://example.org/ns/type#One> .
-
-<res2>
-    a <https://example.org/ns/type#Two> .
-```
-
-Note: the aggregation process is not currently recursive, therefore it will not
-apply to children containers.
-
 ### Alternative: using SPARQL
 
 Another possible way of reading and writing data is to use SPARQL. Currently,