you don't know the rest

what you're not getting is that `/:whateverness/or-other` certainly works for whomever but it's also a constraint, a constraint that is being [added] about something in stuff happening between an administration of the things

it's not rest-ful because it's adding conformity to an already uniform interface, no matter if it is by consensus "pretty" or "vanity" according to the visualization of the information network

that's only telling people the api is rest-ful. it's concealing one way of expressing the endpoint as opposed to the other façan de parler. why? why do you want to constrain the complexity of the expressible, rather than promote its categorical heterogeneity? what do you need all your presumably cool urls to look ontologically homogenous of the syntax of the real and not like flowers looking like they're being looked at by flowers?

```
example.app/:api/...
```

```
example.app/api.html?
```

```
example.app?([.*])...&
```

```
example.app/:content-word...
```

```
....example.service.app/:word?api=list
```

```
example.app/api/:content-word
```

```
example.app?api/:service-word
```

```
www.app#api/:service-word
```

with what does the inquiring mind want to know?

what the...