I have a website which hosts web documents & web applications and also acts as an origin server for documents and applications that are served to a client via a proxy web site.

I'm finding it quite difficult to **find the correct names to model the players in the http request** in my server-side application.

For example, Hypertext Transfer Protocol (RFC 2616) describes the parts of an HTTP URL as:

```
http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]] 

```

Whereas RFC 1738 uses this terminology to define the parts of an URL:

```
An HTTP URL takes the form:
      http://<host>:<port>/<path>?<searchpart>

```

Lets say I want show an *advert* next to some *primary content* on a *web page* that is hosted on my *origin server*. 

I would want to tell the *complementary content server* to find the best advert to suit the *primary content* and render them both together as *the resource* which is served up at an URL.

One of my biggest problems finding the **correct** words to differentiate between:

* the client-facing-URL (the web address that someone might type into the browser bar - ie. <http://example.com/mydocument?page=2>) (I am calling this *the canonical URL* at the moment)
* the origin-server-URL (the address that the gateway server calls upon to get the page i.e. <http://originserver.example.co.uk/version2/mydocument?page=2>)
* the actual content at the canonical URL (which is always changing)
* the revision of that piece of actual content at that URL
* the name of the thing that defines the link between the URL and the current content (the *semantic placeholder* / or praps the *semantic specification*) - i.e. <http://example.com/mydocument> means ''a list of books relating to hockey''
* page 2 of the content at the canonical URL
* page 2 of the content shown by the application after a filter has been applied
* etc, etc

I have heard that there are books written to define domain specific languages for various industries. 

and there are books like Fowler's *Analysis Patterns: Reusable Object Models* (which i have not read).

So my question is :

**Are there any books/website/published models that summarise all the w3c specs, best practice, SEO termininology and wrap it all up into nice 'n' handy a published object model that can be a truly ubiquitous language for web applications that I can adopt for my web app?**

Basically something to cut the ambiguity.

links:
RFC 1738 (<http://www.ietf.org/rfc/rfc1738.txt>)
HTTP/1.1 RFC 2616 (<http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.2.2>)