\documentclass[12pt,titlepage]{article}

\usepackage{amsmath}
\usepackage{mathrsfs}
\usepackage{amsfonts}
\usepackage{amssymb}
\usepackage{amsthm}
\usepackage{mathtools}
\usepackage{graphicx}
\usepackage{color}
\usepackage{ucs}
\usepackage[utf8x]{inputenc}
\usepackage{xparse}
\usepackage{hyperref}

%----Macros----------
%
% Unresolved issues:
%
%  \righttoleftarrow
%  \lefttorightarrow
%
%  \color{} with HTML colorspec
%  \bgcolor
%  \array with options (without options, it's equivalent to the matrix environment)

% Of the standard HTML named colors, white, black, red, green, blue and yellow
% are predefined in the color package. Here are the rest.
\definecolor{aqua}{rgb}{0, 1.0, 1.0}
\definecolor{fuschia}{rgb}{1.0, 0, 1.0}
\definecolor{gray}{rgb}{0.502, 0.502, 0.502}
\definecolor{lime}{rgb}{0, 1.0, 0}
\definecolor{maroon}{rgb}{0.502, 0, 0}
\definecolor{navy}{rgb}{0, 0, 0.502}
\definecolor{olive}{rgb}{0.502, 0.502, 0}
\definecolor{purple}{rgb}{0.502, 0, 0.502}
\definecolor{silver}{rgb}{0.753, 0.753, 0.753}
\definecolor{teal}{rgb}{0, 0.502, 0.502}

% Because of conflicts, \space and \mathop are converted to
% \itexspace and \operatorname during preprocessing.

% itex: \space{ht}{dp}{wd}
%
% Height and baseline depth measurements are in units of tenths of an ex while
% the width is measured in tenths of an em.
\makeatletter
\newdimen\itex@wd%
\newdimen\itex@dp%
\newdimen\itex@thd%
\def\itexspace#1#2#3{\itex@wd=#3em%
\itex@wd=0.1\itex@wd%
\itex@dp=#2ex%
\itex@dp=0.1\itex@dp%
\itex@thd=#1ex%
\itex@thd=0.1\itex@thd%
\advance\itex@thd\the\itex@dp%
\makebox[\the\itex@wd]{\rule[-\the\itex@dp]{0cm}{\the\itex@thd}}}
\makeatother

% \tensor and \multiscript
\makeatletter
\newif\if@sup
\newtoks\@sups
\def\append@sup#1{\edef\act{\noexpand\@sups={\the\@sups #1}}\act}%
\def\reset@sup{\@supfalse\@sups={}}%
\def\mk@scripts#1#2{\if #2/ \if@sup ^{\the\@sups}\fi \else%
  \ifx #1_ \if@sup ^{\the\@sups}\reset@sup \fi {}_{#2}%
  \else \append@sup#2 \@suptrue \fi%
  \expandafter\mk@scripts\fi}
\def\tensor#1#2{\reset@sup#1\mk@scripts#2_/}
\def\multiscripts#1#2#3{\reset@sup{}\mk@scripts#1_/#2%
  \reset@sup\mk@scripts#3_/}
\makeatother

% \slash
\makeatletter
\newbox\slashbox \setbox\slashbox=\hbox{$/$}
\def\itex@pslash#1{\setbox\@tempboxa=\hbox{$#1$}
  \@tempdima=0.5\wd\slashbox \advance\@tempdima 0.5\wd\@tempboxa
  \copy\slashbox \kern-\@tempdima \box\@tempboxa}
\def\slash{\protect\itex@pslash}
\makeatother

% math-mode versions of \rlap, etc
% from Alexander Perlis, "A complement to \smash, \llap, and lap"
%   http://math.arizona.edu/~aprl/publications/mathclap/
\def\clap#1{\hbox to 0pt{\hss#1\hss}}
\def\mathllap{\mathpalette\mathllapinternal}
\def\mathrlap{\mathpalette\mathrlapinternal}
\def\mathclap{\mathpalette\mathclapinternal}
\def\mathllapinternal#1#2{\llap{$\mathsurround=0pt#1{#2}$}}
\def\mathrlapinternal#1#2{\rlap{$\mathsurround=0pt#1{#2}$}}
\def\mathclapinternal#1#2{\clap{$\mathsurround=0pt#1{#2}$}}

% Renames \sqrt as \oldsqrt and redefine root to result in \sqrt[#1]{#2}
\let\oldroot\root
\def\root#1#2{\oldroot #1 \of{#2}}
\renewcommand{\sqrt}[2][]{\oldroot #1 \of{#2}}

% Manually declare the txfonts symbolsC font
\DeclareSymbolFont{symbolsC}{U}{txsyc}{m}{n}
\SetSymbolFont{symbolsC}{bold}{U}{txsyc}{bx}{n}
\DeclareFontSubstitution{U}{txsyc}{m}{n}

% Manually declare the stmaryrd font
\DeclareSymbolFont{stmry}{U}{stmry}{m}{n}
\SetSymbolFont{stmry}{bold}{U}{stmry}{b}{n}

% Manually declare the MnSymbolE font
\DeclareFontFamily{OMX}{MnSymbolE}{}
\DeclareSymbolFont{mnomx}{OMX}{MnSymbolE}{m}{n}
\SetSymbolFont{mnomx}{bold}{OMX}{MnSymbolE}{b}{n}
\DeclareFontShape{OMX}{MnSymbolE}{m}{n}{
    <-6>  MnSymbolE5
   <6-7>  MnSymbolE6
   <7-8>  MnSymbolE7
   <8-9>  MnSymbolE8
   <9-10> MnSymbolE9
  <10-12> MnSymbolE10
  <12->   MnSymbolE12}{}

% Declare specific arrows from txfonts without loading the full package
\makeatletter
\def\re@DeclareMathSymbol#1#2#3#4{%
    \let#1=\undefined
    \DeclareMathSymbol{#1}{#2}{#3}{#4}}
\re@DeclareMathSymbol{\neArrow}{\mathrel}{symbolsC}{116}
\re@DeclareMathSymbol{\neArr}{\mathrel}{symbolsC}{116}
\re@DeclareMathSymbol{\seArrow}{\mathrel}{symbolsC}{117}
\re@DeclareMathSymbol{\seArr}{\mathrel}{symbolsC}{117}
\re@DeclareMathSymbol{\nwArrow}{\mathrel}{symbolsC}{118}
\re@DeclareMathSymbol{\nwArr}{\mathrel}{symbolsC}{118}
\re@DeclareMathSymbol{\swArrow}{\mathrel}{symbolsC}{119}
\re@DeclareMathSymbol{\swArr}{\mathrel}{symbolsC}{119}
\re@DeclareMathSymbol{\nequiv}{\mathrel}{symbolsC}{46}
\re@DeclareMathSymbol{\Perp}{\mathrel}{symbolsC}{121}
\re@DeclareMathSymbol{\Vbar}{\mathrel}{symbolsC}{121}
\re@DeclareMathSymbol{\sslash}{\mathrel}{stmry}{12}
\re@DeclareMathSymbol{\bigsqcap}{\mathop}{stmry}{"64}
\re@DeclareMathSymbol{\biginterleave}{\mathop}{stmry}{"6}
\re@DeclareMathSymbol{\invamp}{\mathrel}{symbolsC}{77}
\re@DeclareMathSymbol{\parr}{\mathrel}{symbolsC}{77}
\makeatother

% \llangle, \rrangle, \lmoustache and \rmoustache from MnSymbolE
\makeatletter
\def\Decl@Mn@Delim#1#2#3#4{%
  \if\relax\noexpand#1%
    \let#1\undefined
  \fi
  \DeclareMathDelimiter{#1}{#2}{#3}{#4}{#3}{#4}}
\def\Decl@Mn@Open#1#2#3{\Decl@Mn@Delim{#1}{\mathopen}{#2}{#3}}
\def\Decl@Mn@Close#1#2#3{\Decl@Mn@Delim{#1}{\mathclose}{#2}{#3}}
\Decl@Mn@Open{\llangle}{mnomx}{'164}
\Decl@Mn@Close{\rrangle}{mnomx}{'171}
\Decl@Mn@Open{\lmoustache}{mnomx}{'245}
\Decl@Mn@Close{\rmoustache}{mnomx}{'244}
\makeatother

% Widecheck
\makeatletter
\DeclareRobustCommand\widecheck[1]{{\mathpalette\@widecheck{#1}}}
\def\@widecheck#1#2{%
    \setbox\z@\hbox{\m@th$#1#2$}%
    \setbox\tw@\hbox{\m@th$#1%
       \widehat{%
          \vrule\@width\z@\@height\ht\z@
          \vrule\@height\z@\@width\wd\z@}$}%
    \dp\tw@-\ht\z@
    \@tempdima\ht\z@ \advance\@tempdima2\ht\tw@ \divide\@tempdima\thr@@
    \setbox\tw@\hbox{%
       \raise\@tempdima\hbox{\scalebox{1}[-1]{\lower\@tempdima\box
\tw@}}}%
    {\ooalign{\box\tw@ \cr \box\z@}}}
\makeatother

% \mathraisebox{voffset}[height][depth]{something}
\makeatletter
\NewDocumentCommand\mathraisebox{moom}{%
\IfNoValueTF{#2}{\def\@temp##1##2{\raisebox{#1}{$\m@th##1##2$}}}{%
\IfNoValueTF{#3}{\def\@temp##1##2{\raisebox{#1}[#2]{$\m@th##1##2$}}%
}{\def\@temp##1##2{\raisebox{#1}[#2][#3]{$\m@th##1##2$}}}}%
\mathpalette\@temp{#4}}
\makeatletter

% udots (taken from yhmath)
\makeatletter
\def\udots{\mathinner{\mkern2mu\raise\p@\hbox{.}
\mkern2mu\raise4\p@\hbox{.}\mkern1mu
\raise7\p@\vbox{\kern7\p@\hbox{.}}\mkern1mu}}
\makeatother

%% Fix array
\newcommand{\itexarray}[1]{\begin{matrix}#1\end{matrix}}
%% \itexnum is a noop
\newcommand{\itexnum}[1]{#1}

%% Renaming existing commands
\newcommand{\underoverset}[3]{\underset{#1}{\overset{#2}{#3}}}
\newcommand{\widevec}{\overrightarrow}
\newcommand{\darr}{\downarrow}
\newcommand{\nearr}{\nearrow}
\newcommand{\nwarr}{\nwarrow}
\newcommand{\searr}{\searrow}
\newcommand{\swarr}{\swarrow}
\newcommand{\curvearrowbotright}{\curvearrowright}
\newcommand{\uparr}{\uparrow}
\newcommand{\downuparrow}{\updownarrow}
\newcommand{\duparr}{\updownarrow}
\newcommand{\updarr}{\updownarrow}
\newcommand{\gt}{>}
\newcommand{\lt}{<}
\newcommand{\map}{\mapsto}
\newcommand{\embedsin}{\hookrightarrow}
\newcommand{\Alpha}{A}
\newcommand{\Beta}{B}
\newcommand{\Zeta}{Z}
\newcommand{\Eta}{H}
\newcommand{\Iota}{I}
\newcommand{\Kappa}{K}
\newcommand{\Mu}{M}
\newcommand{\Nu}{N}
\newcommand{\Rho}{P}
\newcommand{\Tau}{T}
\newcommand{\Upsi}{\Upsilon}
\newcommand{\omicron}{o}
\newcommand{\lang}{\langle}
\newcommand{\rang}{\rangle}
\newcommand{\Union}{\bigcup}
\newcommand{\Intersection}{\bigcap}
\newcommand{\Oplus}{\bigoplus}
\newcommand{\Otimes}{\bigotimes}
\newcommand{\Wedge}{\bigwedge}
\newcommand{\Vee}{\bigvee}
\newcommand{\coproduct}{\coprod}
\newcommand{\product}{\prod}
\newcommand{\closure}{\overline}
\newcommand{\integral}{\int}
\newcommand{\doubleintegral}{\iint}
\newcommand{\tripleintegral}{\iiint}
\newcommand{\quadrupleintegral}{\iiiint}
\newcommand{\conint}{\oint}
\newcommand{\contourintegral}{\oint}
\newcommand{\infinity}{\infty}
\newcommand{\bottom}{\bot}
\newcommand{\minusb}{\boxminus}
\newcommand{\plusb}{\boxplus}
\newcommand{\timesb}{\boxtimes}
\newcommand{\intersection}{\cap}
\newcommand{\union}{\cup}
\newcommand{\Del}{\nabla}
\newcommand{\odash}{\circleddash}
\newcommand{\negspace}{\!}
\newcommand{\widebar}{\overline}
\newcommand{\textsize}{\normalsize}
\renewcommand{\scriptsize}{\scriptstyle}
\newcommand{\scriptscriptsize}{\scriptscriptstyle}
\newcommand{\mathfr}{\mathfrak}
\newcommand{\statusline}[2]{#2}
\newcommand{\tooltip}[2]{#2}
\newcommand{\toggle}[2]{#2}

% Theorem Environments
\theoremstyle{plain}
\newtheorem{theorem}{Theorem}
\newtheorem{lemma}{Lemma}
\newtheorem{prop}{Proposition}
\newtheorem{cor}{Corollary}
\newtheorem*{utheorem}{Theorem}
\newtheorem*{ulemma}{Lemma}
\newtheorem*{uprop}{Proposition}
\newtheorem*{ucor}{Corollary}
\theoremstyle{definition}
\newtheorem{defn}{Definition}
\newtheorem{example}{Example}
\newtheorem*{udefn}{Definition}
\newtheorem*{uexample}{Example}
\theoremstyle{remark}
\newtheorem{remark}{Remark}
\newtheorem{note}{Note}
\newtheorem*{uremark}{Remark}
\newtheorem*{unote}{Note}

%-------------------------------------------------------------------

\begin{document}

%-------------------------------------------------------------------


\section*{General Discussion}

\hypertarget{general_discussion}{}\section*{{General Discussion}}\label{general_discussion}

Below we used to discuss general issues concerning the $n$Lab. But it seems that we found a consensus that \emph{discussion} (as opposed to incremental work on entries) is best hosted at the blog, not the wiki. So now you are encouraged to post any messages concerning the $n$Lab community to:

\begin{itemize}%
\item the blog entry \href{http://golem.ph.utexas.edu/category/2009/01/nlab_general_discussion.html}{nLab -- General Discussion}, or
\item the \href{http://www.math.ntnu.no/~stacey/Mathforge/nForum/}{n-Forum}

\end{itemize}
This probably means that you should \textbf{not edit this page here} any further. If you want to follow up on a discussion that started below, consider summarizing the state of the discussion at the above blog entry and then post your contribution there.


\vspace{.5em} \hrule \vspace{.5em}
\hypertarget{embedding_questions_about_unclear_text_via_abbreviation_tags}{}\paragraph*{{Embedding questions about unclear text via abbreviation tags?}}\label{embedding_questions_about_unclear_text_via_abbreviation_tags}

Bruce Bartlett says: Take a look at what I did at [[integration over supermanifolds]]. I'm using the hovertext feature to embed a question over the phrase ``since odd graded differential 1-forms, being of total even degree, do not have a top exterior power''\ldots{} if your mouse lingers over this. Maybe this is an idea?

Urs Schreiber says: That's a great idea! I have replied to your question in that entry now (check it out!) which means that the mouse-over effect is currently no longer visible (it still is present in the source code there, so everybody can check how this works: where did you leanr about this feature??), but let's consider sticking to that kind of inserting questions.

\hypertarget{slash_lab_entries}{}\paragraph*{{Slash lab entries?}}\label{slash_lab_entries}

\emph{Bruce Bartlett says:} I have the vague idea that mathematical entries (like [[integration over supermanifolds]] should have a ``/lab'' section where ``lab'' things get done, like a tutorial class. I don't know what that means.

\emph{Urs Schreiber say:} I don't know either! We are likely to have entries of very different nature, some of them just reviewing very standard stuff, some summarizing less well-known stuff, and in some areas we may want to think about new stuff, even. I think as long as every single page makes clear where the information presented there comes from, everything is okay.

\hypertarget{singleauthor_areas}{}\paragraph*{{Single-Author Areas}}\label{singleauthor_areas}

Instiki can run multiple Wikis (``Webs'' in the Instiki Parlance). Urs, John and David have the password required to create additional Webs.

\begin{itemize}%
\item Webs can be password-protected, so that only those in posession of the password can edit them.
\item A password-protected Web can be ``published'' so that others can read, but not edit, the contents. (Or, of course, they can remain unpublished, so that the authors can carry out their \emph{super sekrit} machinations in private).

\end{itemize}
These two features provide the possibility for single-author areas, where one person (or persons: whoever has the requisite password) is in authorial control.

Here is [[johnbaez:HomePage|John's area]].

\hypertarget{importing_css}{}\paragraph*{{Importing CSS}}\label{importing_css}

I propose that, at least in these early days of the $n$Lab, that the CSS style sheet be tweakable by everyone. I propose the following mechanism to do this.

Here is a publically editable CSS file: \href{http://ncatlab.org/nlab/files/general.css}{general.css}. I want the stuff in here to piggyback onto the existing CSS declarations in instiki.css (as can be found by clicking on ``Edit Web'' on the main page).

Basically, one just needs to add the following line to the beginning of that file:

\begin{verbatim}@import url('/nlab/files/general.css');\end{verbatim}
\textbf{Not a chance}. That would be a \emph{completely unacceptable} security risk.

That way everyone is free to make some tweaks. The point is that Markdown has a nice CSS trick, which \href{[http://golem.ph.utexas.edu/~distler/blog/archives/001820.html}{Jacques used to create the Theorem environments}. The idea is that if one types eg.

\begin{verbatim}+-- {: my_gismo}
Some text here.
=--\end{verbatim}
then one gets a div element whose class is ``my\_gismo''. So in the CSS file general.css, we can style this block anyway we want.

If that's all you want to do, you don't need access to the site's CSS file. You can use a combination of \href{http://maruku.rubyforge.org/proposal.html}{Maruku's metadata format} and the {\colorbox[rgb]{1.00,0.93,1.00}{\tt style}} attribute to style your responses. (See the Markdown source of this page, to see how it's done.) Inline styles are \href{http://golem.ph.utexas.edu/~distler/blog/archives/001181.html}{sanitized for your protection}.

I see that you've already noticed the existence of Maruku's metatdata format, though your example is slightly incorrect.

For instance, I created a ``query'' block, which I'm using to ask questions on Urs's pages (beware I will use it on \emph{yours} soon dear reader!). See [[integration over supermanifolds]]. (The query block will only display as green once that adjustment I suggested is made to the instiki.css file by someone with a password by clicking on Edit Web and then Stylesheet tweaks, to change the instiki.css file)

More generally, for changing the overall look-and-feel, it would be nice to introduce theme-support for Instiki, just as we already have theme support for \href{http://golem.ph.utexas.edu/instiki/show/S5}{slide shows} within Instiki.

Trying to reupload the general.css file: [[general.css:file]]

Darn, I was worried it might not work. Darn, that causes problems. This is a silly thing about Instiki --- you can't replace uploaded files with new ones. Jacques? Any suggestions?

An interface for managing uploaded files is another item on the \href{http://golem.ph.utexas.edu/instiki/show/TODO}{TODO list}.

Yes you're right --- thanks. [[Bruce Bartlett]]

\hypertarget{formatting_of_discussions}{}\subsection*{{Formatting of discussions}}\label{formatting_of_discussions}

\emph{Urs Schreiber says:} We need to do something about this: it is already becoming hard to recognize, read, let alone follow the flow of discussions.

Let's agree on some kind of basic formatting rules for how to type personal speech here and, in particular, as comments into the other entries. I like Jacques' way of formatting his comments above. Maybe everybody should choose his or her color and then always insert comments using this kind of formatting with this kind of color.

\emph{Jacques says:} I hope you don't mind, but I darkened the colour of your response. Bright green is hard on the eyes, when it occurs in large blocks of running text. Besides, it's the colour of hyperlinks on this wiki, which is a little confusing.

\emph{Bruce Bartlett says:} Ok\ldots{} that's a bit of a weird system for discussion, but I'm okay to go along with it\ldots{} However, I'm quite fond of the green ``query'' block that I put on [[integration over supermanifolds]], as below:

\emph{Question:} Okay, but what is the \emph{differential $d\theta_1$ of an odd co-ordinate function}? How are we to think of it geometrically? Does it measure a rate of change of something? (Bruce Bartlett)

\emph{Answer:} See [[superdifferential form]]. (Urs Schreiber)

I think that a lot of people (for instance Simon) maybe aren't that keen on writing stuff for the $n$Lab right at this moment, but certainly have a lot of questions about Urs's stuff. I see this query feature as a way for them to get involved. Place query blocks all over Urs's text :-) (sorry Urs!)

I see these query blocks as staying on the page for a while (even after they are answered by Urs or someone else), because it makes people feel better when they see that they are not the only ones who didn't understand the material. At some point they can be taken down on any given page.

However, I would really like it if some of this CSS code would go directly into instiki.css, instead of us having to reproduce it on each page. That is not a workable solution.

Thus I propose the following: if anyone has some CSS code that they would like to promote, email it to someone with a password (Urs, John, David, Jacques) and ask them to put it in via the ``Edit Web'' button.

\emph{Jacques said:} I agree. Once people have settled on a particular styling convention for content, it should go in the ``Stylesheet Quirks'' section of the ``Edit Web'' page, where it will automatically be reproduced on every page of this Web. Technically, that's \emph{not} the {\colorbox[rgb]{1.00,0.93,1.00}{\tt instiki\char46css}} file. The latter is common to all instiki installations.

My point was that experimentation on this front does not require access to the site-wide stylesheet, since Instiki provides a convenient way to specify inline styles on a per-page, or per-element basis (as demonstrated here).

Please settle on something that everyone likes and the (and only then) add it to the Site-wide ``Stylesheet Tweaks''.

I'm quite fond of messing around with colours, etc. and without this feature I feel a bit deflated :-)

For instance, I think it would be great to use CSS so as to style downloadable documents correctly, as \href{http://reference.sitepoint.com/css/css3attributeselectors}{explained here}. The idea is that every pdf link will have a tiny pdf icon next to it, and more importantly every n-category cafe link will have a tiny n-category cafe logo next to it; the same for arXiv links, etc.

Another thing I'd like to try in CSS is to set Georga (a serif font) as the main text (and math) font for the $n$Lab. Try it for a few days and see.

\emph{Urs says}: Bruce, I like the look of those query boxes. Graphical sophistication like that greatly improves the look-and-feel of the wiki.

You should explain at some promint point of the wiki, probably at the [[HowTo]] page what people need to do to insert such gadgets.

Concerning contributions by others: let's see how it develops. I'd really enjoy having several people contributing here, eventually. But on the other hand it is also maybe good if we as the hosts have a bit of time to produce some context here first.

I am hoping that eventually I will produce enough nonsense here that others can't stand it anymore and jump in to help out ;-)

Seriously, if it turns out that a few of us produce most of the content but many others contribute many little improvements, like correcting small mistakes, adding references, asking for clarifications or voicing other requests, establishing cross-links, etc., I'd already be happy.

Toby Bartels is currently doing this already, which is great.

\emph{Bruce says:} Okay. Yes I agree with you about the content; for a while the site will be dominated by you putting up your stuff on $L_\infty$ integration, etc. But that's great, that serves a very valuable purpose. It creates a central repository of \emph{expository} stuff (note expository\ldots{} it musn't be written in an encyclopeadic way\ldots{} that's important I think). Then when you make a post at the n-category cafe, you can refer to this stuff.

\emph{Urs says:} I am not sure about that thing about me ``dominating'' the site. I'll expect that as soon as John posts his first marvelous exposition things will change rapidly. So far I mainly invested energy to provide pages for all the keywords I just used in \href{http://golem.ph.utexas.edu/category/2008/12/zhu_on_lies_second_theorem_for.html}{this} blog post.

For me that's one of the points of having this wiki here: that we establish a stable resource where we can refer to in entries without having to rehash all old disacussions in every new entry.

And in any case, one point about the wiki as opposed to the blog is also that there is no ``title page'' which can be dominated, but every reader is free to follow whichever way he prefers through the site, and ignore the content he or she is not interested in.

Concerning expository versus encyclopedic: I want both. In the best of all worlds each page is structured roughly similarly, with a section ``basic idea'' at the beginning, an expository part in the middle, and a concise and comprehensive list of the main definitions and facts at the end. Or the like.

But, you know. This requires work. And time. We'll get there.

\emph{Bruce says:} Ok I've uploaded the new stylesheet tweaks. Now if you link to an arXiv, n-category cafe, pdf, or a \emph{page} inside a pdf file, a little icon will appear, like this:

\href{http://arxiv.org/abs/q-alg/9503002}{arXiv link}, \href{http://golem.ph.utexas.edu/category/2008/11/tom_leinster_in_the_reasoner.html#c020641}{n-category caf\'e{} link}, \href{http://www.math.uni-hamburg.de/home/schreiber/sin.pdf}{pdf file}, \href{http://www.math.uni-hamburg.de/home/schreiber/sin.pdf#page=4}{\emph{page} in pdf file}.

If you \emph{don't} want that icon to appear (I can imagine a number of reasons why not), there is a temporary workaround: capitalize one of the important letters:

\begin{itemize}%
\item For pdf and page-in-pdf files, capitalize something in ``pdf''.
\item For n-category cafe files, capitalize something in ``http://golem.ph.utexas.edu/category''.
\item For arXiv links, capitalize something in ``http://arxiv.org/''.

\end{itemize}
Also, the query box is now in the stylesheet. If you want to make a query box, just type

\begin{verbatim}+-- {: .query}

_Question_: Why did the chicken cross the road?

=--\end{verbatim}
in the text and you'll get out:

\emph{Question}: Why did the chicken cross the road?

\hypertarget{categories}{}\subsection*{{Categories}}\label{categories}

Those of you writing here must have noticed it, but I've put little category tabs at the bottom of some pages (such as this one). The first one was category: people, put on [[Jacques Distler]] by Jacques himself, and I just followed that. I think that the categories are self explanatory; you can find them all from the `All Pages' link (or click on `category: meta' below).

I've just created category: redirect and trying to apply a few \href{http://golem.ph.utexas.edu/category/2008/11/nlab.html#c020626}{naming conventions}. Let me know (say with a query comment [[Toby Bartels|here]]?) if I do anything wrong.

Anyway, in the future, it may be useful also to have content-related categories, but that may want to wait until we know better what the shape of the content here will be.

---Toby

I've noticed on several pages that some links have been created with partial words highlighted, e.g. [[coalgebra|coalgebra]]ic, endo[[functor]], etc. When I see that, my brain instinctively flashes a warning sign and I am tempted to ``fix'' it by replaing the partial highlights with [[coalgebra|coalgebraic]], [[functor|endofunctor]], etc. Is this by design? Would anyone object to my ``fixing'' it? Just curious\ldots{} [[Eric Forgy|Eric]]

I presume your fix is to replace

 with

. The latter produces the desired ``[[coalgebra|coalgebraic]]'' link, instead of the bizarre-looking ``[[coalgebra]]ic''. If so, I say: go ahead. ---[[Jacques Distler]]

I produce such links purely out of laziness. By all means fix them (as Jacques describes). ---Toby

I always fix them. I hate `em. - [[John Baez|John]]

\hypertarget{naming_conventions}{}\subsection*{{Naming conventions}}\label{naming_conventions}

I talked with Urs about naming conventions \href{http://golem.ph.utexas.edu/category/2008/11/nlab.html#c020626}{here}. To be complete, here are the naming conventions that I propose (and which I have, for now, imposed on every page currently in the wiki): * Page titles should be nouns. If you want an adjective that normally modifies the same noun, then use the entire noun phrase. If you want an adjective that applies to many different contexts, then try adding `-ness' to make a noun. If you want a verb, then try adding `-ing' or `-ation' to make a noun (example: [[categorification]]. * Page titles should be uncapitalised, except for word words that are always capitalised. (Examples: [[light mill]], but [[Lie algebra]].) * Page titles should be singular, unless the phrase usually occurs in the plural (so effectively a mass noun or a collective noun, rarely if ever referring to individuals). Examples: [[Lie groupoid]], but [[Lie's three theorems]]. * Titles should follow standard American English spelling conventions. Examples: [[internalization]] (with `z'), [[omega-category]] (with hyphen as in $\omega$-category) but [[BRST complex]], [[Chevalley?Eilenberg algebra]] (with endash since they are two people) but [[Burali-Forti paradox]] (with hyphen since he is one person).

---Toby (who prefers British spelling, but Urs and John use American)

Yes sir! ---Bruce

I trust you're joking, Bruce, but I hope that nobody gets hard-nosed about these conventions, at least not yet. They are just suggestion, good ones I hope, but it's not too late to change or reject them, and the whole community should be involved in that.

Also, thanks for the comment style. I see now how they're made!

---Toby

Sorry, I haven't been keeping up, lots of other stuff on, but just stuck my nose through the door to see how the decorating is going. With regard to these naming conventions I tried to rename the Math page Mathematics to get round the US/UK thing, I now see it has been renamed. Keep up the good work. ---Simon

Thanks, Toby, for your efforts! I appreciate it. These naming convention suggestions are good. If and when I do not adhere to them, it is because of me not paying enough attention to what my fingers are doing, which happens. -- Urs

Then I guess that I'll correct you whenever you violate the conventions. But as Jacques would point out, the wiki will be less cluttered if the actual creation of new pages always follows the conventions; that's the most important part. ---Toby

Another possible naming convention: only ASCII characters. It's possible to put non-ASCII characters in a name (but not ones generated by iTeX or {\colorbox[rgb]{1.00,0.93,1.00}{\tt \char38}}\ldots{}{\colorbox[rgb]{1.00,0.93,1.00}{\tt \char59}} character entities), but this may be difficult, depending on the user. We're already applying this in cases like [[omega-category]] (rather than [[∞-category]]), but this idea would go further: to \emph{overrule} the one about following standard spelling when that uses non-ASCII characters (principally dashes). In particular, while the rules above favour [[Chevalley?Eilenberg algebra]] (with endash), this proposed change would favour [[Chevalley-Eilenberg algebra]] (with hyphen) instead. Personally, I prefer the endash, but I can see that this may just expect too much of the writer.

A very fundamental little issue: should we usually write n-category or $n$-category? -[[John Baez|John]]

I would say `$n$-category'. However, that doesn't work in links: `[[$n$-category]]', `[[n-category|$n$-category]]'. So for that I write `$n$-[[n-category|category]]'. In any case, we should be happy to accept contributions from people that say `n-category'; somebody that cares more can always pretty it up afterwards. ---[[Toby Bartels|Toby]]

\hypertarget{stylesheet_update_removing_icons_in_links}{}\paragraph*{{Stylesheet update: removing icons in links}}\label{stylesheet_update_removing_icons_in_links}

I disabled the icons that used to appear next to pdf files, n-category cafe links, etc., by commenting out that code in the CSS for the nLab under ``Edit Web'' on the main page.

It's just a test. I was starting to feel that the little images were a distraction on the page, sort of like the feeling you get when there are too many advertisements on a page. How do people feel, or you in favour of them or not? They can be enabled again by just un-commenting them in the stylesheet tweaks by someone with a password. -- Bruce

I liked them. -Urs

\hypertarget{basic_math_entries_diagrams}{}\subsection*{{Basic Math Entries, Diagrams}}\label{basic_math_entries_diagrams}

I'm glad people are tackling all sorts of fundamental issues in this discussion. I've been keeping quiet mainly because I'm really busy, and prefer to spend my little time here creating new entries.

I am very proud to be the first to create the entries for basic words like [[object]], [[morphism]], [[category]], [[adjunction]] and so on - it's like being God and coming up with the first star, the first rock and so on. Other people may think it silly to have entries for such basic ideas, but I'm hoping this website will eventually grow into a complete introduction to $n$-category theory. If and when I ever start writing my books on higher-dimensional algebra, I'll do it here, and include lots of link to pages where basic terms are defined. So, I imagine we're planting seeds that will eventually grow into something quite large.

For this reason, I hope that Todd Trimble joins this project, as he once said he wanted to. I also hope Tom Leinster and Eugenia Cheng and Simon Willerton and Robin Houston and many other folks contribute entries.

I need to figure out a way to lure such people into adding new entries - and improving ones that already exist. I may try some $n$-Cafe posts that basically say: ``Hey, I just wrote a little entry on monoidal categories! Can you help improve it?''

How easy is it to just grab a Wikipedia entry, fix it up a bit, and stick it in here? What are our legal and/or moral obligations if we do that?

See \href{https://secure.wikimedia.org/wikipedia/en/wiki/Wikipedia%3ACopyrights#Reusers.27_rights_and_obligations}{what Wikipedia has to say}. ---[[Toby Bartels|Toby]]

Here's another serious issue: how easy or impossible is it to draw \emph{diagrams} in this environment? Without diagrams, we're crippled.

-[[John Baez|John]]

Ya mean like this one (from the page on [[oriental|orientals]]):

\begin{displaymath}
\itexarray{\arrayopts{\rowalign{center}}
O(\Delta^0) = & \{ 0\} \\
O(\Delta^1) = & \left\{ 0 \to 1\right\} \\
O(\Delta^2) = & \left\{
\itexarray{ }
\right\}\\
O(\Delta^3) = & \left\{
\itexarray{ }\right\}\\
O(\Delta^4) = & \left\{
\itexarray{ }
\right\}
}
\end{displaymath}
--- [[Jacques Distler|Jacques]]

\emph{[[John Baez|John]] says}: Since all my papers in \LaTeX\xspace  use \LaTeX\xspace  macro package like xypic to draw diagrams, it's quite sad that we need to use something like SVG here. It means I can't take material from my expository papers and put it on the $n$Lab without redrawing all the diagrams. And, it means I can't use this environment to write papers without redrawing all the diagrams. Sigh.

\hypertarget{backups}{}\subsubsection*{{Backups}}\label{backups}

I think it was mentioned before, but I missed it: is there a quick web-interface way to upload files to the server that an entry wants to link to?

Another thing: the more work we invest in this the more I become worried that we have some data loss. Is there any way too have an automated mirror image of the site created every now and then? Jacques said the whole wiki itself sits in one big file. What about pictures etc on the server that it links to?

-Urs

Urs writes: ``The more work we invest in this the more I become worried that we have some data loss'' - yes, I'm worried about that too. I'd imagined you had already solved that problem by now! I think I won't do any more work on this wiki until we solve this problem. I hate losing work, and I back up all my work to 2 or 3 sites.

``Jacques said the whole wiki itself sits in one big file.'' Is there at least a way for you or I to manually copy this file to another site? Of course an automatic backup procedure is better - until it stops working for some reason; one still needs to check it regularly.

-[[John Baez|John]]

Well, you'll have to ask your webhosts why

\begin{verbatim} scp -v /usr/local/instiki/db/production.db.sqlite3 distler@golem.ph.utexas.edu:Desktop/\end{verbatim}
produces the following error (lots of other junk, but this is the important line):

\begin{verbatim} debug1: read_passphrase: can't open /dev/tty: No such device or address\end{verbatim}
which is a little strange, since

\begin{verbatim}  ls -l /dev/tty\end{verbatim}
yields

\begin{verbatim}  crw------- 1 root root 5, 0 Dec 14 06:32 /dev/tty\end{verbatim}
One should also be able to initiate a {\colorbox[rgb]{1.00,0.93,1.00}{\tt scp}} operation \emph{from} the remote machine. That doesn't work either, presumably for the same reason.

Can one make use of the Atom feeds (see `Feeds' at top)? I don't really know anything about feeds, but I probably should learn.

You can \href{http://ncatlab.org/nlab/export}{export} the entire wiki. That's not the point. You should also be able to mirror the database file and any attendant files

\begin{verbatim}scp -r /usr/local/instiki/public/nlab/files distler@golem.ph.utexas.edu:Desktop/\end{verbatim}
to some remote location (your laptop, even). That's not possible because the setup here seems not to assign a {\colorbox[rgb]{1.00,0.93,1.00}{\tt tty}} to the shell one obtains when one {\colorbox[rgb]{1.00,0.93,1.00}{\tt ssh}}s into the VPS. This makes it impossible to use {\colorbox[rgb]{1.00,0.93,1.00}{\tt scp}} (or {\colorbox[rgb]{1.00,0.93,1.00}{\tt rsync\char32\char45e\char32ssh}} or whatever).

To John: So there is no reason to be worried about loss of the content of the entries. Please don't make this stop anyone work on the wiki!! As Jacques points out, using \href{http://ncatlab.org/nlab/export}{export} gives a zip-file with all the typed content. I am keeping regular backup copies of that.

But I was wondering what happens when we start uploading lots of auxiliary files, such as .gifs, to the server. Apparently that requires more thoughts/work\ldots{}

To Toby: subscribing to the feed is a convenient way to keep track of which entries were changed in which way.

-- [[Urs Schreiber|Urs]]

So if we want to back up the current wiki, then we export it. If we want to back up the wiki and its history, then we (once only) go through the history of each page and back it up by hand, then use the feed to track all further changes. If we want to back up uploaded files too, will these show up in the feed or the export? (Do we have any yet for a test?)

That's a \emph{silly} way to do things. Just {\colorbox[rgb]{1.00,0.93,1.00}{\tt cp}} the database file into the {\colorbox[rgb]{1.00,0.93,1.00}{\tt \char47usr\char47local\char47instiki\char47public\char47nlab\char47files\char47}} directory, download the copy with your web browser, and then delete the copy.

Heh, maybe I should say that's how \emph{I} could do it ({\tt \symbol{94}}\_{\tt \symbol{94}}). I don't want to make assumptions about what can be done in the shell, which apparently has some bad behaviour. In any case, I don't have access to the shell, but I am capable of the (otherwise much sillier) method above. (Not that I expect to do that either \ldots{} although I did export the wiki last night and might do so again in a week or so.)

I understand. I presumed that Urs would be the one doing the off-site backups. In any case, I want to emphasize that placing a copy of the database file in the downloadable {\colorbox[rgb]{1.00,0.93,1.00}{\tt files}} directory is a security risk. So it should not be named something obvious, like ``{\colorbox[rgb]{1.00,0.93,1.00}{\tt production\char46db\char46sqlite\char51}}'', and it should not be left there any longer than absolutely necessary.

If Urs is reading this, then he will probably do that (until {\colorbox[rgb]{1.00,0.93,1.00}{\tt scp}} is fixed), and that will settle it. But by the way, what is the security risk in the database? (Backups are more secure if widely spread, and without your warning, Urs might even have invited others to download it, although doubtless he, John, and David would be more than sufficient.) Does it contain my unencrypted password or something? (Of course, feel free to link to a general Instiki page if you've already explained this elsewhere.)

Unencrypted passwords (including the Instiki password needed on the ``{\colorbox[rgb]{1.00,0.93,1.00}{\tt Edit\char32Web}}'' page) and all the purportedly password-protected data.

As far as avoiding the danger of lost effort, I think that the problem is solved. But backing up will be much easier and smoother if the {\colorbox[rgb]{1.00,0.93,1.00}{\tt tty}} problem is solved too.

One operation instead of three.

\hypertarget{uploading_resources}{}\section*{{Uploading resources}}\label{uploading_resources}

I was going to upload some pictures, but I am experiencing problems sft-ing into the server. Not sure why.

Generally, it would be nice if everybody could upload resources together with the entries he or she submits. Maybe with a password protection. I am not sure how to proceed on this matter\ldots{}

-- [[Urs Schreiber|Urs]]

\href{http://golem.ph.utexas.edu/instiki/show/File+Uploads}{Jacque says} that one shouldn't allow uploads without password protection, I guess to prevent spam. Perhaps uploads should be restricted to a separate web (for uploads only), which this web can link to. (I gather that allowing uploads and requiring passwords is done web by web within the Instiki installation.)

Uploaded files can also overwhelm the memory limits (even without spam). That's one reason to make images SVG whenever possible.

If you keep a reasonable upper limit on the allowed size of uploaded files and if someone is willing to check periodically that miscreants are not abusing the site by using it as a file drop-box, then I suppose the risk is relatively low. Nowadays, with the popularity of P2P filesharing systems, the temptation of using some random unsecured website as a drop-box is somewhat diminished.

\hypertarget{another_category_another_naming_convention}{}\subsection*{{Another category, another naming convention}}\label{another_category_another_naming_convention}

I've gone through all the names of categories (like $\Set$, the category of sets) and tagged the pages category: category. Also, I've imposed a naming convention on categories, that they should be singular and abbreviated if long. I'm not sure that I agree with these, but they seemed to be more common already than the alternatives, and I think that it will be good to have a convention. If anybody doesn't like this convention, then please say so! (It's not too late to change things back.) ---[[Toby Bartels|Toby]]

\hypertarget{algebroids}{}\subsection*{{Algebroids}}\label{algebroids}

\emph{[[Eric Forgy|Eric]] says}:

I was thinking about the categorical definition of [[algebra|algebras]] as a [[monoid]] in Vect. Then I was trying to think of how you would similarly define a [[graded algebra]]. A thought that came to mind, which seems to make sense, is that a graded algebra could be thought of as a ``category in Vect''. Or something like that.

Come to think of it, could you say that given a monoid $M$, an algebra is a functor $A:M\to Vect$?

Could you say that given a category $C$, an algebroid is a functor $A:C\to Vect$?

Then a graded algebra is a special kind of algebroid. It sounds kind of poetic. Is there any truth to it?

Does that make any sense?

After some doodling, I think that a graded algebra should be a monoid in the category of graded vector spaces. Is that better?

If a graded algebra is a monoid in graded vector spaces, what is a clean ``categorical'' way to probe the degree of the element?

What is a clean categorical way to define graded vector spaces?

\emph{[[Urs Schreiber|Urs]] says}: If you want you can say that a $G$-graded vector space is a functor $G \to Vect$. Notice: NOT a functor $\mathbf{B}G \to Vect$ from the group $G$, regarded as a one-object [[groupoid]], but just a functor from the underlying [[set]] of $G$.

\emph{[[Toby Bartels|Toby]] says}: Given an [[abelian group]] $G$, the [[functor category]] of functors from $|G|$ to $\Vect$ (where $|G|$, the order of the group $G$, is a [[set]]) is the category of $G$-graded vector spaces with homogeneous linear maps as morphisms. To make this a [[monoidal category]], let $(V \otimes W)_g$ (where $V = (V_g)_{(g:G)}$ is a functor) be

\begin{displaymath}
\bigoplus_{h:G} V_h \otimes W_{g-h} = \bigoplus_{h,k:G, \atop h+k=g} V_h \otimes W_k
\end{displaymath}
(a kind of [[convolution product]]). Then a $G$-graded algebra should be a monoid in this monoidal category. (To some extent, this should still work even if $G$ is just a non-abelian monoid. What we really need is to describe that convolution product arrow-theoretically.)

See also: \href{https://secure.wikimedia.org/wikipedia/en/wiki/Super_vector_space#The_category_of_super_vector_spaces}{https\char58\char47\char47secure\char46wikimedia\char46org\char47wikipedia\char47en\char47wiki\char47Super\char95vector\char95space\char35The\char95category\char95of\char95super\char95vector\char95spaces}. But it looks like $G$ must be a ring (or at least rig) to define the braiding.

\emph{[[John Baez|John]] says}: Eric wrote:

\emph{I was thinking about the categorical definition of [[algebra|algebras]] as a [[monoid]] in Vect. Then I was trying to think of how you would similarly define a graded algebra.}

It's a monoid in GradedVect, the monoidal category of graded vector spaces.

\emph{A thought that came to mind, which seems to make sense, is that a graded algebra could be thought of as a ``category in Vect''. Or something like that.}

No, a category in Vect is precisely a `Baez-Crans 2-vector space': it has a vector space of objects, a vector space of morphisms, and all the category operations are linear.

\emph{Come to think of it, could you say that given a monoid $M$, an algebra is a functor $A:M\to Vect$?}

You could say it, but that wouldn't make it true. 

In fact, a functor $A: M \to Vect$ is none other than a [[representation]] of the monoid $M$.

\emph{Could you say that given a category $C$, an algebroid is a functor $A:C\to Vect$?}

You could say it, but that wouldn't make it true. 

In fact, a functor $A: C \to Vect$ is a [[representation]] of your category $C$, which is very different than an algebroid. An [[algebroid]] is a category enriched in $Vect$.

\emph{Then a graded algebra is a special kind of algebroid. It sounds kind of poetic. Is there any truth to it?}

Yes, there's some truth to this guess, despite the errors that led up to it. Jim Dolan and I have been working on ideas related to this, and (more interestingly) their applications to algebraic geometry. But we prefer to shock the world with these ideas at a later time.

\emph{What is a clean categorical way to define graded vector spaces?}

Toby already answered this, but let me note that one can and should define [[graded vector space|$S$-graded vector spaces]] for any set $S$; these then acquire special properties when $S$ is a monoid (like the natural numbers) or a group (like the integers). An $S$-graded vector space is a functor $F: S \to Vect$, where we think of the set $S$ as a [[discrete category]].

Please don't take my slapdowns the wrong way! I'm very glad you're trying to understand lots of math from a categorical viewpoint. But, in my `Wizard' persona it's my duty to crush errors --- with a certain crazed glee, and utter disregard for the sensitive feelings of the victim.

[[Eric Forgy|Eric]] says: Thanks! Fortunately (I think), I am comfortable admitting I don't understand something and one way I learn is to state things as I see them hoping to be corrected. Slap away!

\emph{[[Eric Forgy|Eric]] says}: If a group is a groupoid with one object, is an algebra an algebroid with one object? I've never seen a definition of \emph{algebroid}, which is why I guessed an algebroid would be something like a category in $Vect$ as opposed to a monoid in $Vect$. I drew some doodle diagrams which seemed to make sense. Is a `Baez-Crans 2-vector space' another word for algebroid, i.e. is a `Baez-Crans 2-vector space' with one object an algebra? It seems to be as far as I can tell.

Mathieu says: I don't think so, because a category in Vect with one object is a monoid in Vect for the monoidal structure given by the \emph{cartesian} product, whereas an algebra is a monoid for the monoidal structure given by the \emph{tensor} product. In fact, on each vector space there is a unique monoid structure for the cartesian product, given by the codiagonal, so a Baez-Crans 2-vector space with one object is just a vector space.

\hypertarget{discussion_pages}{}\subsection*{{Discussion Pages}}\label{discussion_pages}

On some pages, e.g. [[quiver]], some discussion is forming. Rather than polluting the page and rather than just deleting the discussion after it has been settled, what if we create special ``Discussion'' pages that relate to specific pages? For example,

 and link to this page from

.

If we decide to do this, we may want to settle now on a proper page title format.

That's a possibility. However, I don't think that ongoing discussions are pollution, certainly not when they're in their query blocks, easy to separate from the rest of the page.

A lot of discussion will have no value worth saving (and it's in the edit history if really needed). A lot of useful discussion can be refactored (when finished) into the normal page text. Until we get into back-and-forth arguments and haggled compromises like on Wikipedia, I'm not sure what would be left to move to a dedicated discussion page.

\emph{[[John Baez|John]] says:}

Right now I like the idea of putting the discussion in the same page, at the end, in a section labelled Discussion.

I think that people can learn a lot from these discussions, where you see the interplay of ideas better than in the formal portion of the text. This is, after all, not an encyclopedia but a ``Lab'' - a place where people come to work and think. We haven't quite discovered what that means yet. But, it could involve a lot of discussion.

Yeah, I also like these Discussion sections at the bottom.

\hypertarget{definitions__boldface_or_italics}{}\subsection*{{Definitions --- Boldface or Italics}}\label{definitions__boldface_or_italics}

\emph{[[John Baez|John]] says}:

I've been putting definitions in \emph{italics}. Someone else is putting them in \textbf{boldface}. We should settle on a convention. Meet me at dawn in the town square --- bring your pistol.

If you used the \href{http://golem.ph.utexas.edu/instiki/show/Theorems}{Theorem Environment} to mark then up, then this decision could be made globally, by adjusting the CSS. But, since I've pointed this out 6 or 8 times, now, maybe I should just let you have recourse to your pistols.

\emph{[[Eric Forgy|Eric]] says}: I'm still learning and wasn't aware of the Theorem Environment. We should definititely encourage its use, however, I think John is referring to the first use of the word \emph{within} a definition. I've noticed that too. I've been using \textbf{bold}, but could switch to \emph{italic} if that is what you want.

\emph{[[John Baez|John]] says}: In this case I'm more interested in consistency than enforcing my will upon the world, despite my joke about pistols at dawn. \textbf{Bold} jumps out you more than \emph{italics}, I think. A theorem environment would let us make (and change) this decision globally, but we won't want all our definitions to be stated as part of a formal \textbf{Definition} environment --- sometimes it's nice to make a definition as part of a paragraph of ordinary text, and in my own papers I always put the defined term in \textbf{boldface}, to 1) make the definitions easy to spot, and 2) make it clear that I'm defining something instead of stating a fact about something (I hate it when someone says ``Pr\"u{}fer rings are hereditary and Noetherian'' and I can't tell if this is supposed to be the \emph{definition}, or merely a cute \emph{fact} about Pr\"u{}fer rings).

I also prefer boldface. I've been doing that unless a page already uses italics. ---[[Toby Bartels|Toby]]

\emph{[[Eric Forgy|Eric]] says}: Lots of new pages are cropping up with \emph{italics} instead of \textbf{bold}. I've been changing them when I see them. From now, the first time a word being defined is used within the definition, let's make it \textbf{bold}.

\emph{[[John Baez|John]] says}: whoops! I've been continuing to use italics. I'll switch to \textbf{bold}.

\emph{[[Eric Forgy|Eric]] says}: No worries. It's great to see all the new content :) I was just beginning to wonder if I SHOULD be changing them to \textbf{bold}. Reviewing this discussion, though, I think we settled on \textbf{bold}. To keep things consistent, I'll continue to switch things as I come across them. Things are really starting to take shape! I'm learning just by editing stuff.

\emph{[[John Baez|John]] says}: Thanks for all the great work! I see you improved my picture of a [[span]]. That inspired me to improve the entry on spans, and add one on [[pullbacks|pullback]] - my first tiny stab at explaining [[limit|limits]] on the $n$Lab.

\hypertarget{linking_to_wikipdia}{}\subsection*{{Linking to Wikip\ae{}dia}}\label{linking_to_wikipdia}

\emph{[[Eric Forgy|Eric]]} says: How would I link to an external address that itself contains parentheses, e.g.

http://en.wikipedia.org/wiki/Field\_(mathematics)

Attempting

picks up the first closing parentheses and tries to link to

http://en.wikipedia.org/wiki/Field\_(mathematics

produces \href{http://en.wikipedia.org/wiki/Field_%28mathematics%29}{Field}.

\emph{[[John Baez|John]] says}: I ran into this problem too, but not remembering the good solution described above, I adopted a crude hack: I left out the parentheses around, say, ``(mathematics)''. It worked, but only because Wikipedia forgave my sin. I need to go back and fix my mistakes someday.

\hypertarget{deleting_pages}{}\subsection*{{Deleting Pages}}\label{deleting_pages}

I created a page on accident (typo) and didn't realize until I modified it. Is there a way to delete it?

\href{http://golem.ph.utexas.edu/instiki/show/Edit+Web#delete}{Yes}.

Eric must be talking about {\colorbox[rgb]{1.00,0.93,1.00}{\tt \char91\char91action\char32group\char93\char93}} (don't link it!). I just put it in {\colorbox[rgb]{1.00,0.93,1.00}{\tt category~\char58\char32delete}}, so anybody with the password to the wiki can delete it by deleting all orphaned pages in that category. On the other hand, you could leave it there (blanked), since it doesn't seem to do any harm.

Jacques just added several more pages to the {\colorbox[rgb]{1.00,0.93,1.00}{\tt delete}} category, some of which were not created as either mistakes or as redirect pages, although all of them were created extremely short. It seems like a waste of time, and a slippery slope to start deleting authorship information for \emph{short} items (most of which will now be attributed to [[Toby Bartels|me]], actually), but nobody will be seriously confused.

I added orphan pages from the {\colorbox[rgb]{1.00,0.93,1.00}{\tt redirect}} category which \emph{never} (going back all the way through their history) contained any actual content, \emph{except} for a redirect link to another page.

In fact, there were a couple of similar pages that (at some point in the past) contained a link to \emph{two} pages. Those I left unmolested, as I did all of the pages in the {\colorbox[rgb]{1.00,0.93,1.00}{\tt redirect}} category that, at one point, contained actual content that has subsequently moved elsewhere. Those are, at the very least, of antiquarian interest.

Anyone who feels that any of the aforementioned pages lie on the wrong end of the slippery slope is encouraged to revert them.

OK, I reverted all of the ones that don't seem to me to fit the criterion that you mentioned. That is, I reverted all of the ones that originally contained a link to a resource on another website, or that contained an outline of a broad topic that happened to consisted of no more than one item at the time. Equivalently ---although this was not the standard that I used---, I reverted all those that contained material that David or Urs wrote and which Urs or I copied to a renamed page.

The phrase `slippery slope' is probably not the best. My point is it can be difficult to determine which information is worth keeping and which is not, which is why it's often best to keep all of it. Sometimes this takes extra effort, and then you might not bother; sometimes there are reasons why it can't all be kept, such as space constraints. Here, it is easy and feasible to keep it.

Eric's page is a little different, since he (in effect) created in blank and wants to delete it himself; if he could have deleted it just as he erased the content that was presumably there on his first save, then nobody would ever have noticed except him. But perhaps it was I who started on the slippery slope, and you who followed \ldots{}.

Anyway, if anybody deletes anything, it will probably be Urs; I'll accept whatever he does, even if I happen to think that it was a poor decision. I'm not the boss.

\emph{[[Eric Forgy|Eric]] says}: I like the idea of regularly deleting pages marked

. This would also give us a mechanism to delete pages we create by accident. I guess there would be a danger of malicious deleting if it was automated?

\hypertarget{linking_to_external_papers}{}\subsection*{{Linking to External Papers}}\label{linking_to_external_papers}

\emph{[[Eric Forgy|Eric]] says}: When a paper becomes freely available on some web page, I'm pretty sure it is ``public'' and there would be no harm in us providing our own copy. Is that right? If so, I had the thought that it might be better to upload a commonly referenced PDF rather than link to an external link. The reason being that the external link may become broken and the paper would no longer be available. If we had our own copy of popularly referenced papers here, the links would never become broken. Just an idea\ldots{}

As a matter of copyright law, it's not true that freely available papers are in the public domain. Providing our own copy is probably still legal (at least if the server is in the U.S.), since we'd provide it for educational purposes and there's no money involved on either end. That said, if there's any chance that someone might request that we remove it, we should have somebody designated to act on such requests.

However, there are other problems. PDF files are much larger than plain text, and we may have space problems if we try to copy a lot. Also, we'll miss any new version that appear, especially common on the arXiv. As for dead links, while they are the curse of the Web, one can guard against those by keeping a copy of what one might like to read again on one's own personal computer. Then if a link here dies, you can decide case by case whether it's wise to upload it here.

We have 16GB free space on the server. Let's upload things which we find important enough to be uploaded.

Wow! I think that I was remembering the RAM limits discussed on the Caf\'e{}. 16GB ought to be enough for everything ({\tt \symbol{94}}\_{\tt \symbol{94}}).

\hypertarget{why_globular_identities}{}\subsection*{{Why globular identities?}}\label{why_globular_identities}

I'm ``secretly'' (as if it weren't totally obvious) trying to learn enough of the material here at the nLab to be able to frame some of the stuff Urs and I worked on into the context of [[space and quantity]], but where both space and quantity are ``discrete''. So far I've learned some cool ways (but totally obvious to anyone here) to define [[directed graph|directed graphs]] and I attempted to generalize it to [[directed n-graph|directed n-graphs]] hoping to make a connection to higher categories somehow. However, one barrier for me has been the [[globular set|globular identities]] because the shapes they produce are ``globs'' or ``bigons'' which are not what I want for geometrical modeling. I've recently learned about [[double category|double categories]] and they (and their higher dimensional generalizations) seem to be closer to what I'm looking for. In the process of learning about double categories, I've also stumbled onto [[enriched category|bicategories]] as being enriched over [[Cat]], but Urs corrected my Example by specifying that what is really enriched over $Cat$ are strict 2-categories. He then added another example, i.e. a strict $n$-category as being enriched over strict $(n-1)$-categories and stated that as $n\to\infty$ you get $\omega$-[[omega-category|categories]]. This latter example gives some hint as to why the globular identities are there. Is that essentially why $\omega$-categories are defined with globular identities so that you can iterate the construction via enrichment? Any words of wisdom/clarification on the subject or even pointers to further references for [[geometric definition of higher category|geometrical definitions of higher categories]] other than those based on simplices (maybe cubes?) would be appreciated. - [[Eric Forgy|Eric]]

\emph{[[Eric Forgy|Eric]] says}: By the way, Urs has created a page that begins and mostly ends an answer to the question about shapes here: [[geometric shapes for higher structures]]

\hypertarget{organizing_the_pages}{}\section*{{Organizing the Pages}}\label{organizing_the_pages}

\emph{[[John Baez|John]]} says: In email, David Corfield asked: ``I wonder how we can encourage different levels of explanation. A few slick comments gets a concept across to an expert, while more is needed for the non-expert. Might there be parallel pages for the same entry?

Urs replied: ``At least on some entries we already tried to offer different level of explanations. A couple of entries start with a section `Idea' that offers some heuristic ways to tink about the concept. Then comes the formal `Definition' and then after that some helpful `Remarks' etc. I'd think this kind of approach can be used to provide information of use for a wide range of readers.''

I replied: ``Multiple pages are a bit awkward\ldots{} Wikipedia does fairly well at this with just one page, and we can do even better, just by starting with easy stuff and working our way up to harder stuff.

Urs has described how some pages, and eventually all, will have several sections. However, Urs seems to like focusing on high-level folks, while I focus on low-level folks. So, ultimately, it won't be enough to have just one section called ``The Idea''. What ``the idea'' is depends on how much you know. So, ultimately, the page should start with a very low-level description of the idea, and later move on to more and more sophisticated versions.

This will take a while to develop. I haven't really begun to invest any serious energy in the $n$Lab, since I've been busy finishing papers.

So, for example, my entry on rings beginning with ``a ring is a monoid in Ab'' was just a cold splash of water meant to wake up people who aren't used to category theory. A more sane entry would remind people of the usual definition and then explain how it can be compressed this way. But this would take longer to write.

I'm even imagining a fiendish plan where I force my grad students to write $n$Lab articles on topics they're learning about. Not sure that's a good idea.

I'm gonna post this on the nLab general discussion page - that's where this conversation should really be occuring.``

By the way, this General Discussion page needs a table of contents, with links, for people to find information on different topics. It's sprawling out of control. It's also possible we should use \emph{other} pages for talking about specific math topics like Algebroids or Globular Identities. Maybe we need a Math Discussion page and a Physics Discussion page?

[[Urs Schreiber|Urs]] says: I was going to address this, too: this discussion page here does not work well. It is hard to see where the last contribution is.

But there is an obvious answer: we want \emph{discussion on the blog}, don't we? The blog is designed to allow discussion, the wiki to allow incremental collaborative work. We should have our ``general discussion'' on the $n$Lab over at the $n$Cafe. The additional advantage would be that everybody reading the blog will always be alerted of the discussion which we are having here.

\emph{[[Eric Forgy|Eric]] says}: Oh oh! I like the idea of moving the ``General Discussion'' to the nCafe. That makes a lot of sense. ``There to chat, here to work.'' If something in the General Discussion becomes elevated to actual content, we can always add that content to the nLab, where it will be indexed, etc.

As far as the level of discussion, my opinion is that we should avoid duplicating ``standard'' definitions as much as possible (especially material that is already on wikipedia) and take this opportunity to present everything arrow theoretically. I almost think of it as a challenge to define every item via diagrams with as few words as possible.

Now that I think of it, there already is an nLab article on the nCafe which is suitable as a General Discussion and some questions I asked here should have probably been asked there. Sorry about that. This page could serve as a summary of anything there worth keeping.

This very discussion is \href{http://golem.ph.utexas.edu/category/2008/12/organizing_the_pages_at_nlab.html}{now at the Caf\'e{}}!

\emph{[[John Baez|John]] says:} Okay, good: move most of the General Discussion to the $n$Caf\'e{}!

This General Discussion page has, embedded in the general discussion, a number of important how-to tips and useful conventions (like how to spell $n$-category). \emph{This} stuff deserves a page or two here at the $n$Lab. Maybe some energetic young person can create that. [[HowTo]]

category: meta

[[!redirects general discussion]] [[!redirects General discussion]] [[!redirects General Discussion]]



\end{document}