categories - Category Theory list
 help / color / mirror / Atom feed
From: Steve Vickers <s.j.vickers@cs.bham.ac.uk>
To: Toby Bartels <toby+categories@ugcs.caltech.edu>, categories@mta.ca
Subject: Re: patenting colimits?
Date: Wed, 27 May 2009 17:08:29 +0100	[thread overview]
Message-ID: <E1M9WFM-0000qZ-Rq@mailserv.mta.ca> (raw)

Toby Bartels wrote:
> ...
> Certainly much of what is in the patent application is obvious,
> but perhaps not all of it; were these diagrams of diagrams a new idea?,
> or was applying them to computer system specifications a new idea?.
> ...

Dear Toby,

The idea of treating specifications as colimits is a few decades old
now. Burstall and Goguen used it in their categorical account of their
specification language Clear, with a specification used to construct a
new theory as colimit of others.

The hierarchical step, diagrams of diagrams, was studied by Catherine
Oriat in her thesis and (I believe) a TCS paper in 2000. My own student
Gillian Hill investigated a variant of this (PhD Thesis 2002; also two
papers with me, 2001, 2006), replacing the category of finite diagrams
over a base category C by the equivalent category of finitely presented
presheaves. Both are finite cocompletions, but a presheaf presentation
by generators and relations comes over neatly as a "configuration by
components and sharing". For obvious reasons the iterated construction
"flattens" back down to the single one (the construction is a KZ-monad
in the 2-category of categories). Gillian also investigated a
multi-level configuration language that maintains the hierarchical
structure without flattening (configurations of configurations of
configurations of ...) and includes cross-level specification morphisms.
However, we did not persevere to work out the categorical semantics of
this, nor did we make a computer implementation.

Regards,

Steve Vickers.


[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


             reply	other threads:[~2009-05-27 16:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 16:08 Steve Vickers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-02 10:38 Dusko Pavlovic
2009-06-02  8:51 Till Mossakowski
2009-05-30 12:07 Zinovy Diskin
2009-05-29 19:57 Dusko Pavlovic
2009-05-29  1:24 Toby Bartels
2009-05-28 21:07 Dusko Pavlovic
2009-05-28 15:49 Uwe.Wolter
2009-05-28  7:15 David Espinosa
2009-05-27 19:33 Toby Bartels
2009-05-27 19:22 Toby Bartels
2009-05-27 16:18 mjhealy
2009-05-27 16:12 David CHEMOUIL
2009-05-27 11:29 zoran skoda
2009-05-27  7:28 David CHEMOUIL
2009-05-27  6:21 soloviev
2009-05-27  3:29 Zinovy Diskin
2009-05-27  2:53 David Spivak
2009-05-26  4:46 Dusko Pavlovic
2009-05-26  1:20 Eduardo J. Dubuc
2009-05-26  0:04 Toby Bartels
2009-05-26  0:04 Greg Meredith
2009-05-25 23:53 Michael Barr
2009-05-25 21:11 Toby Bartels
2009-05-25 18:53 Vaughan Pratt
2009-05-25 13:35 Ronnie Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1M9WFM-0000qZ-Rq@mailserv.mta.ca \
    --to=s.j.vickers@cs.bham.ac.uk \
    --cc=categories@mta.ca \
    --cc=toby+categories@ugcs.caltech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).