John Panzer (http://abstractioneer.org)
On Sat, Jul 12, 2008 at 3:40 PM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
And another question that arrised while implementing the atom
entry /
feed bit.
In the examples the entry always includes the namespace:
<appdata xmlns="http://opensocial.org/2008/opensocial";>
<pokes>3</poke>
<last_poke>2008-02-13T18:30:02Z</last_poke>
</appdata>
However in the feed output it doesn't:
<appdata>
<pokes>3</poke>
<last_poke>"2008-02-13T18:30:02Z"</last_poke>
</appdata>
Is that intentional?
No, this looks like another typo :)
On Jul 13, 2008, at 12:37 AM, Chris Chabot wrote:
>
> Oh while being pedantic, i ran into a few small typo's in the
> document:
>
> "<author><url>uurn:guid:example.org:58UIDCSIOP233FDKK3HD44</url></
> author>"
> should be: s/uurn/urn
>
> application/json representation (with indexBy=id):
> .. json example ...
> application/atom+xml representation:
> .. would expect an example here of how indexBy work work in the
atom
> representation, but to my eyes it seems to be just a regular
entry and
> no indexBy's applied to it?
>
>
> "The default representation of a collection is simply a JSON
list of
> records ([ {...}, {....}, ...]). The special type "index" means
that
> the collection is instead to be represented as a mapping, using
the
> index field; this is requested by supplying a query parameter
> "indexBy" (see below). "
>
> Actually in the document its ABOVE and not below :)
>
> ps is the uurn:guid:<Real ID> required? from an app development
> perspective just the raw ID value would seem easier to me.. but
i'm no
> atom expert yet so i might be missing something obvious.
>
> -- Chris
>
>
> On Jul 13, 2008, at 12:02 AM, David Primmer wrote:
>
>>
>> You're right Chris, the spec has 'hosting' rules that do not
cover
>> the
>> required fields in author:
>> atom:entry/atom:author/atom:uri aliases "userId"
>>
>> author is a person construct
>> http://atompub.org/rfc4287.html#atomPersonConstruct
>> and requires name, as you mention. the spec only includes uri
>>
>> I posted what I thought was a more complete example of an
activity
>> here:
>>
http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/9f7cbb93d187763e/63ca4da4cedeea7f
>>
>> I didn't run it through validation, but I did just now and
found some
>> of the issues you mention in your feeds and more.
>>
>> You have your content tags flipped around. content should be a
child
>> of entry and it's required, unless you have an alternate link
(that's
>> the third error you got)
>>
>> this is a spec example:
>>
>> <entry xmlns="http://www.w3.org/2005/Atom";>
>> <content type="application/xml">
>> <person xmlns="http://ns.opensocial.org/2008/opensocial";>
>> <name>
>> <unstructured>Jane Doe</unstructured>
>> </name>
>> ..etc...
>>
>>
>>
>> On Sat, Jul 12, 2008 at 2:27 PM, Chris Chabot <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> To validate what i've got so far in the atom/rest
implementation in
>>> the php version of shindig I've been running the output
through http://validator.w3.org/feed/
>>>
>>> Everything checks out except for 3 things:
>>> * line 20, column 4: Undefined author element: url [help]
>>> <url>urn:guid::1</url>
>>> * line 21, column 2: Missing author element: name [help]
>>> </author>
>>> *line 24, column 0: Missing content or alternate link [help]
>>> </entry>
>>>
>>> In other words it doesn't dig the URL in the author, but would
>>> rather
>>> see a NAME there; Plus it's complaining that there's no
'alternate'
>>> link.
>>>
>>> Is this a case of ignore and move on, or something we could /
should
>>> improve upon?
>>>
>>> -- Chris
>>>
>>> ps, the output i was validating is:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <entry xmlns="http://www.w3.org/2005/Atom";>
>>> <person xmlns="http://ns.opensocial.org/2008/opensocial";>
>>> <content type="application/xml">
>>> <isOwner></isOwner>
>>> <isViewer></isViewer>
>>> <name>
>>> <familyName>Chabot</familyName>
>>> <givenName>Chris</givenName>
>>> <unstructured>Chris Chabot</unstructured>
>>> </name>
>>> <id>1</id>
>>> <thumbnailUrl>http://www.partuza.nl/images/people/1.96x96.jpg
</
>>> thumbnailUrl>
>>> </content>
>>> </person>
>>> <title>fetch people[1]</title>
>>> <author>
>>> <url>urn:guid::1</url>
>>> </author>
>>> <updated>2008-07-12T23:19:38+02:00</updated>
>>> <id>urn:guid::1</id>
>>> </entry>
>>>
>>>
>>>>
>>>
>>
>>
>
>
