Return-Path: 
 <dev-return-24700-apmail-cordova-dev-archive=cordova.apache.org@cordova.apache.org>
X-Original-To: apmail-cordova-dev-archive@www.apache.org
Delivered-To: apmail-cordova-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 033F2C6FD
	for <apmail-cordova-dev-archive@www.apache.org>;
 Tue, 16 Jul 2013 16:02:27 +0000 (UTC)
Received: (qmail 57596 invoked by uid 500); 16 Jul 2013 16:02:26 -0000
Delivered-To: apmail-cordova-dev-archive@cordova.apache.org
Received: (qmail 57489 invoked by uid 500); 16 Jul 2013 16:02:26 -0000
Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cordova.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cordova.apache.org>
List-Post: <mailto:dev@cordova.apache.org>
List-Id: <dev.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list dev@cordova.apache.org
Received: (qmail 57476 invoked by uid 99); 16 Jul 2013 16:02:21 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jul 2013 16:02:21 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of gorkem.ercan@gmail.com
 designates 74.125.83.53 as permitted sender)
Received: from [74.125.83.53] (HELO mail-ee0-f53.google.com) (74.125.83.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jul 2013 16:02:15 +0000
Received: by mail-ee0-f53.google.com with SMTP id c41so482056eek.12
        for <dev@cordova.apache.org>; Tue, 16 Jul 2013 09:01:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=iH1VQaBhViPxX6g63Xzw94ZFVxjCkbNAMY/pxb4kYBg=;
        b=pi6/EnxqV8jPG526nbnEQZsBkcJTCaDZjDWoQ4O1yef8KwILEEfe4MRvxjFu8h+TYW
         juKz9BGvljtPHZkIQK9/2XlQj5KF+OwXOZQOLaktnQ3rj7YOU0tw0Z/yMAfu+AOWOeL6
         u2UcA/gkQee1VxzfG0vWDGlt5jG+1y8HTakywLxLrqzyW5i9z6Efqn9F53CCmEjiowIw
         TIw+01NQ2r72qY9KR2dPWx8zFyY+2vqst3r/0Uis+4H3RvYvykCcNzJtwzuVTdO8yZwA
         kB/uAn2Ffy55VG/c/lOWBiThOL3fIGY+KuqH4IzD6piqfhmS4rVG17M43/cIzQO5t8w7
         9jug==
MIME-Version: 1.0
X-Received: by 10.14.177.8 with SMTP id c8mr2166296eem.93.1373990515574; Tue,
 16 Jul 2013 09:01:55 -0700 (PDT)
Received: by 10.14.216.201 with HTTP; Tue, 16 Jul 2013 09:01:55 -0700 (PDT)
In-Reply-To: <CE0AB92C.227B4%fil@adobe.com>
References: <2D04CA88799BFF41A56DAE6575F62B7E2410E617@XMB111CNC.rim.net>
	<CE0AB92C.227B4%fil@adobe.com>
Date: Tue, 16 Jul 2013 12:01:55 -0400
Message-ID: 
 <CA+X37c=qrSZByUY3WF87TrkZsMK=aM6m3KHvfc64JsamvR9qhw@mail.gmail.com>
Subject: Re: Is a config.xml without an author valid?
From: Gorkem Ercan <gorkem.ercan@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7b621ef29b3b2304e1a31861
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7b621ef29b3b2304e1a31861
Content-Type: text/plain; charset=ISO-8859-1

It should be OK if author is missing. I have tools that does validation and
 moreover it has zero or one occurrence on the spec.
http://www.w3.org/TR/widgets/#the-author-element-and-its-attributes
--
Gorkem


On Tue, Jul 16, 2013 at 11:48 AM, Filip Maj <fil@adobe.com> wrote:

> I think it should be necessary but we never got that far in terms of
> validating config.xml or anything like that
>
> On 7/16/13 8:38 AM, "Jeffrey Heifetz" <jheifetz@blackberry.com> wrote:
>
> >When the config.xml for mobile-spec was re-written recently the <author>
> >element was removed and I'm just wondering if this is valid. In the
> >BlackBerry implementation we've always required one and I'm wondering if
> >this behaviour is wrong, or if I should add one to mobile-spec.
> >
> >Thanks,
> >
> >Jeff
> >
> >---------------------------------------------------------------------
> >This transmission (including any attachments) may contain confidential
> >information, privileged material (including material protected by the
> >solicitor-client or other applicable privileges), or constitute
> >non-public information. Any use of this information by anyone other than
> >the intended recipient is prohibited. If you have received this
> >transmission in error, please immediately reply to the sender and delete
> >this information from your system. Use, dissemination, distribution, or
> >reproduction of this transmission by unintended recipients is not
> >authorized and may be unlawful.
>
>

--047d7b621ef29b3b2304e1a31861--