Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 04565E908 for ; Wed, 20 Feb 2013 18:41:28 +0000 (UTC) Received: (qmail 90771 invoked by uid 500); 20 Feb 2013 18:41:27 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 90752 invoked by uid 500); 20 Feb 2013 18:41:27 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 90743 invoked by uid 99); 20 Feb 2013 18:41:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 18:41:27 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates 209.85.223.181 as permitted sender) Received: from [209.85.223.181] (HELO mail-ie0-f181.google.com) (209.85.223.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 18:41:22 +0000 Received: by mail-ie0-f181.google.com with SMTP id 17so10188608iea.26 for ; Wed, 20 Feb 2013 10:41:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=P1qNJCUDWBLhotzsYQorI8hP3aZs/+c/vDYsgPzHsnI=; b=K2xoDMhi+LfBvJMLZ/fcZH/u/0iNlWkfamYywLuWBhFNME94ZNiWRNw/jxnpgZX9qe Yy/4ZZAEUlO1IXUp40brvrB0cdVxS7gjAwRHAhiOimuG4ZPAuPDe/OGupdcG6oxAeRqv YijOvuB1WjYrjutZj10joaUftTH0iO57ANGz1565ZtzshhM5v9VdHHmlVEzPuDF49FO5 gzLzL1a7Y7fudqYcGdhGCvELgBDv55ORatbe9yQkm/p9tEzSfw+gZVwnBWJIQPxL89Fc ZBEhz78KmMlOmRomgzFq256PugqT+UPnvPXEVn0diyLCKqRYy8vMwntmVKya6vXyMPhl IJAA== MIME-Version: 1.0 X-Received: by 10.43.117.136 with SMTP id fm8mr9730995icc.33.1361385662373; Wed, 20 Feb 2013 10:41:02 -0800 (PST) Received: by 10.50.8.71 with HTTP; Wed, 20 Feb 2013 10:41:02 -0800 (PST) In-Reply-To: References: <055.88e62b912ed293164d9bc776d0fddb17@incubator.apache.org> <51250B28.9050500@wandisco.com> Date: Wed, 20 Feb 2013 13:41:02 -0500 Message-ID: Subject: Re: [Apache Bloodhound] #390: Product wiki syntax From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 2/20/13, Olemis Lang wrote: > On 2/20/13, Gary Martin wrote: >> On 14/02/13 17:34, Apache Bloodhound wrote: >>> #390: Product wiki syntax [...] >> >> My preference is for '/' at this point - the only potential clash that >> springs to mind is with Wiki/Pages but those seem to require some >> specific uppercase rules. >> >> Are there any other problems others can spot? >> > > AFAICR bh/whateever within a wiki page context will be expanded to > relative page . I guess hyphens and/or dots are less problematic > (unless I'm missing something ;) . > jftr ... I'm mainly saying that this will be problematic with the long form e.g. [bh/milestone:m1 caption] -- Regards, Olemis.