Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 545F9178AD for ; Sun, 15 Feb 2015 21:50:28 +0000 (UTC) Received: (qmail 44659 invoked by uid 500); 15 Feb 2015 21:50:16 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 44516 invoked by uid 500); 15 Feb 2015 21:50:16 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 44500 invoked by uid 99); 15 Feb 2015 21:50:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Feb 2015 21:50:16 +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 ansell.peter@gmail.com designates 209.85.213.45 as permitted sender) Received: from [209.85.213.45] (HELO mail-yh0-f45.google.com) (209.85.213.45) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Feb 2015 21:50:12 +0000 Received: by mail-yh0-f45.google.com with SMTP id a41so12523632yho.4 for ; Sun, 15 Feb 2015 13:49:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YsXGGcC0y9yfR8eGTXhMkFy4MkS0Ff3kphFbskbJF98=; b=agALKSpvOT1/1f0gvEvYMekzNxKEQUUeqy3O+Bi0OS4gDv9j/3QyYKrg3UePOlQiv8 L8fkIzjHt3GKKsR3zAYYp2uk/5dxe2F7u/9SYRq+jwqHMk/o4XhzUWAG/aDB4QAaf2R0 k93lmN74zuyqIbvzXd/G7VDUh6jdFmKQfJuqMF60agClvBO7WiesNzgGi6nH2N6lF0CI v6VBeQyzla6kIKBA7pvZz/JQp3jeJnn8eHJCMOruPbrUmq7padzbRc/eeghUgq5iKqlu WDXQB96sYrdT356VqTDg8W/DEQPheGgybDIPuu8Z05QvfwhRBFFR+2hR0H79f68Cvjg2 OgAA== MIME-Version: 1.0 X-Received: by 10.236.210.12 with SMTP id t12mr13849435yho.99.1424036946922; Sun, 15 Feb 2015 13:49:06 -0800 (PST) Received: by 10.170.113.75 with HTTP; Sun, 15 Feb 2015 13:49:06 -0800 (PST) Date: Mon, 16 Feb 2015 08:49:06 +1100 Message-ID: Subject: Design guidelines and SemVer From: Peter Ansell To: Commons Developers List Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On 15 February 2015 at 21:29, Benedikt Ritter wrote: > We like to underline, that we have no experience with the RDF > specification. From a technical point of view we can help to develop the > proposed API (according to our design guide lines [3]). Hi Benedikt, On my personal projects I tend to work from the SemVer specification [5], which isn't oriented to Java specifically, but operates with the same general principles. How open is the Commons project to formally use the SemVer specification as a dependency of the (probably much older) specification published at [3] and expand on it to provide definitions specific to Java. The main reason would be that SemVer, although it has a relatively short history, is fairly widely used across different languages and potentially easier to recognise for outsiders. Cheers, Peter > > [1] http://markmail.org/message/mnlh64qod7cuuj56 > [2] http://markmail.org/message/wl6hpkb4nhsroro5 > [3] http://commons.apache.org/releases/versioning.html > [4] http://markmail.org/message/ylmw7qzx23br4ver [5] http://semver.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org