Return-Path: 
 <abdera-dev-return-918-apmail-incubator-abdera-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-abdera-dev-archive@locus.apache.org
Received: (qmail 78111 invoked from network); 8 Nov 2006 17:50:04 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 8 Nov 2006 17:50:04 -0000
Received: (qmail 85418 invoked by uid 500); 8 Nov 2006 17:50:15 -0000
Delivered-To: apmail-incubator-abdera-dev-archive@incubator.apache.org
Received: (qmail 85395 invoked by uid 500); 8 Nov 2006 17:50:15 -0000
Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:abdera-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:abdera-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:abdera-dev@incubator.apache.org>
List-Id: <abdera-dev.incubator.apache.org>
Reply-To: abdera-dev@incubator.apache.org
Delivered-To: mailing list abdera-dev@incubator.apache.org
Received: (qmail 85386 invoked by uid 99); 8 Nov 2006 17:50:15 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2006 09:50:15 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of jasnell@gmail.com designates
 64.233.184.229 as permitted sender)
Received: from [64.233.184.229] (HELO wr-out-0506.google.com) (64.233.184.229)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Nov 2006 09:50:01 -0800
Received: by wr-out-0506.google.com with SMTP id 58so565837wri
        for <abdera-dev@incubator.apache.org>;
 Wed, 08 Nov 2006 09:49:41 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=jrSXV8LNO5oK5FihhMi69siQnYOkHCS01+FAYAuZQzYrDxVcy3NUeUtJQPkoUGLfvAvX7GDBBzmhQFbFSp5EhhoBYNmFOinW6NPvVwDMjL7AKq3rLEVGw1prvkHIJZE1TsqMAF4wV8rOMfxgvDjfIuzr68Th4rRgbpEA8b+QkCM=
Received: by 10.90.31.19 with SMTP id e19mr2586591age.1163008180974;
        Wed, 08 Nov 2006 09:49:40 -0800 (PST)
Received: from ?192.168.1.101? ( [67.181.218.96])
        by mx.google.com with ESMTP id 13sm14811268wrl.2006.11.08.09.49.38;
        Wed, 08 Nov 2006 09:49:39 -0800 (PST)
Message-ID: <455218A5.4070903@gmail.com>
Date: Wed, 08 Nov 2006 09:49:25 -0800
From: James M Snell <jasnell@gmail.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061025)
MIME-Version: 1.0
To: abdera-dev@incubator.apache.org
Subject: Re: Specification support clarification
References: <7242948.post@talk.nabble.com>
In-Reply-To: <7242948.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

The javadoc is out of date. title used to be an attribute, now it uses
atom:title.  I'm not sure what version of the code you're using. The
code for Workspace and Collection in the HEAD is correct.  I'll update
the javadoc.

- James

Andrei Filimonov wrote:
> I'm working on example code for service document and stuck with the getting
> workspace and collection titles. I appears there is a discrepancy in
> specification support. E.g. javadoc for Workspace interfaces says:
> 
>  * <pre>
>  *  The "app:workspace" element contains information elements about the
>  *  collections of resources available for editing.  The app:workspace
>  *  element MUST contain one or more app:collection elements.
>  *
>  *  appWorkspace =
>  *     element app:workspace {
>  *        appCommonAttributes,
>  *        attribute title { text },
>  *        ( appCollection+
>  *          &amp; extensionElement* )
>  *     }
>  *
> 
> But if you look at the APP draft it is supposed to be:
> 
>    appWorkspace =
>       element app:workspace {
>          appCommonAttributes,
>          ( atomTitle
>            & appCollection*
>            & extensionElement* )
>       }
> 
>    atomTitle = element atom:title { atomTextConstruct }
> 
> The difference is that title is not an attribute but child node.
> Implementation assumes that it is attribute and when I try to parse
> following example from the draft:
> 
> 8.1  Example
> 
>    <?xml version="1.0" encoding='utf-8'?>
>    <service xmlns="http://purl.org/atom/app#"
>             xmlns:atom="http://www.w3.org/2005/Atom">
>      <workspace>
>        <atom:title>Main Site</atom:title>
>        <collection
>            href="http://example.org/reilly/main" >
>          <atom:title>My Blog Entries</atom:title>
>          <categories
>             href="http://example.com/cats/forMain.cats" />
>        </collection>
>        <collection
>            href="http://example.org/reilly/pic" >
>          <atom:title>Pictures</atom:title>
>          <accept>image/*</accept>
>        </collection>
>      </workspace>
>      <workspace>
>        <atom:title>Side Bar Blog</atom:title>
>        <collection
>            href="http://example.org/reilly/list" >
>          <atom:title>Remaindered Links</atom:title>
>          <accept>entry</accept>
>          <categories fixed="yes">
>            <atom:category
>              scheme="http://example.org/extra-cats/"
>              term="joke" />
>            <atom:category
>              scheme="http://example.org/extra-cats/"
>              term="serious" />
>          </categories>
>        </collection>
>      </workspace>
>    </service>
> 
> I get nulls for workspace title. The same problem is with collection titles
> as well. If I change FOMWorkspace implementation to:
> 
>   public String getTitle() {
>     //return getAttributeValue(ATITLE);
> 	  return getText(TITLE);
>   }
> 
> everything works as expected.
> 
> Andrei
> 
> 
>