categories - Category Theory list
 help / color / mirror / Atom feed
From: Dirk Hofmann <dirk@ua.pt>
To: <ptj@maths.cam.ac.uk>
Cc: Maria Manuel Clementino <mmc@mat.uc.pt>,
	Categories mailing list	<categories@mta.ca>
Subject: Re: Non-cartesian closedness of Met
Date: Sat, 17 Dec 2022 09:20:17 +0000	[thread overview]
Message-ID: <E1p6fGU-0000ne-Fc@rr.mta.ca> (raw)

Dear Peter,

we don't have such an example in the paper. Our argument used the 
cartesian closed category of "metric spaces without triangular 
inequality", and showed that, for a metric space X, all 
exponential Y^X (Y metric) taken in that category satisfy the 
triangular inequality if and only if X satisfies that condition.

Best regards
Dirk




On 16 December 2022 at 22:05 GMT+0000, ptj@maths.cam.ac.uk wrote 
...
> Dear Dirk, dear Maria Manuel,
>
> That's very interesting, and I should have remembered it. But 
> did
> your argument come up with an explicit example of a colimit in 
> Met
> not preserved by a functor of the form (-) x Y ?
>
> I suppose I'll have to go and read your paper!
>
> Best regards,
> Peter
>
> On Dec 16 2022, Dirk Hofmann wrote:
>
>>
>>Dear Peter,
>>
>>in our paper
>>
>> - Clementino, M. M., & Hofmann, D. (2006). Exponentiation in
>> $V$-categories. Topology and its Applications, 153(16), 
>> 3113–3128.
>>
>> we give a characterisation of exponentiable metric spaces. The 
>> result
>> essentially states that a metric space (in the sense of 
>> Lawvere) is
>> exponentiable if and only if "there is always a point in the 
>> middle",
>> that is, whenever d(x,z)=u+v, then there is a point y with 
>> d(x,y)≤u+ε
>> and d(y,z)≤v+ε. A finite metric space with a non-trivial 
>> distance
>> cannot be exponentiable.
>>
>>Best regards
>>Dirk
>>
>> On 16 December 2022 at 16:41 GMT+0000, <ptj@maths.cam.ac.uk> 
>> wrote ...
>>> Let Met denote the category of metric spaces and nonexpansive 
>>> maps.
>>> It's well known that if we equip the product of two metric 
>>> spaces
>>> with the L_{\infty} metric (the max of the distances in the 
>>> two
>>> coordinates), we get categorical products in Met; 
>>> alternatively,
>>> if we impose the L_1 metric on the product (the sum of the two
>>> coordinate distances), we get a monoidal closed structure, at 
>>> least
>>> if we weaken the usual definition of a metric by allowing 
>>> metrics to
>>> take the value \infty.
>>>
>>> It's intuitively obvious that the cartesian monoidal structure 
>>> on Met
>>> can't be closed. But I've never (until I wrote one down 
>>> today!) seen
>>> a formal proof of this; does anyone know if it exists anywhere 
>>> in the
>>> literature? My proof is not particularly elegant: it amounts 
>>> to
>>> showing
>>> that a particular coequalizer in Met is not preserved by a 
>>> functor of
>>> the form (-) x Y.
>>>
>>>


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


             reply	other threads:[~2022-12-17  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17  9:20 Dirk Hofmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-18 13:04 ptj
2022-12-16 16:41 ptj
2022-12-19  8:50 ` Jirí Adámek

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=E1p6fGU-0000ne-Fc@rr.mta.ca \
    --to=dirk@ua.pt \
    --cc=categories@mta.ca \
    --cc=mmc@mat.uc.pt \
    --cc=ptj@maths.cam.ac.uk \
    /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).