1) the gd namespace is used to specify elements that are specific to GData
specification, that they are added on top of standard AtomPub elements.2)
Unfortunately you won't be able to specify data with pure e4x, as the GData
server expects to handle data with the current way.
Hope it helps,
Austin
On Dec 17, 2007 4:38 PM, RioVic <vict...@gmail.com> wrote:
All,
I am using the gData calendar API now, with success, thanks to Austin
and some other posters on this group.
Now I am getting into more details, and I have a few questions:
1) Why do some node names have gd: in front of them, while others do
not require this? After all they are all gData fields, right?
2) I want to use exclusively e4x syntax, so I need to know the node
sub-field names of the data values in each node. For example,
<category term="http://schemas.google.com/g/2005#event" scheme="http://
schemas.google.com/g/2005#kind" />
is "pure" e4x, with subfield names 'term' and 'scheme' while,
<title type="text">sample event</title>
is mixed up with an e4x qualifier for sub-field 'type', and the
actual data inside a traditional xml tag <title>blah blah blah</title>
so if I wanted to put that title value in an e4x field, what would it
be called? I have already tried text="sample event" and
valueString="sample event"
This is an advanced question, I know. But all comments are
appreciated.
Thank you,
2 messages in com.googlegroups.google-calendar-help-dataapiRe: XML nodes and consistency of the API