For the /metadata/objects call, is the assumption that only a list of "object names" is returned ? Does Array<ObjectMetadata> contain something like [person, group, department] or does it contain [person{name, title}, group{owner, purpose}] for the most general version of this call ?
How do the following calls differ from each other in what is returned ? /metadata/objects/person vs /metadata/properties/person
The way the spec reads, it isn't clear that the following is not legal (I assume it is not) /metadata/objects/{field} Maybe it is splitting hairs, but it might be better to indicate that if {field} is supplied, the {name} parameter is not optional - unless the intent was to return all objects that implement {field} in which case {name} really is optional.
What is the use case where someone would call the generic /metadata/properties call with no {name} ?
Additional questions:
a) what "data type" is returned for an Object like Person in the
/metadata/objects call (for example) ?
b) what is the difference between "properties" and "fields" ?
c) how are edges in the social graph queried ? or are they assumed
to be "objects" with fields as well ? How are they distinguished from node
objects ?
On Thu, Jul 12, 2012 at 2:12 PM, drobin <drobin1...@gmail.com> wrote:
> Hi,
> Can someone help me understand the "REST-Query-Parameters" piece of the
> meta data incubating section in the Social API Specification ?
> >> ENCODE-REST-PARAMETERS(GetObjects-Request-Parameters)
> A code example would be helpful.
> For the /metadata/objects call, is the assumption that only a list of
> "object names" is returned ?
> Does Array<ObjectMetadata> contain something like [person, group,
> department] or does it contain
> [person{name, title}, group{owner, purpose}] for the most general version
> of this call ?
> How do the following calls differ from each other in what is returned ?
> /metadata/objects/person
> vs
> /metadata/properties/person
> The way the spec reads, it isn't clear that the following is not legal
> (I assume it is not) /metadata/objects/{field} Maybe it is splitting
> hairs, but it might be better
> to indicate that if {field} is supplied, the {name} parameter is not
> optional - unless the intent was
> to return all objects that implement {field} in which case {name} really
> is optional.
> What is the use case where someone would call the generic
> /metadata/properties call with no {name} ?
> Thanks !
> --
> You received this message because you are subscribed to the Google Groups
> "OpenSocial and Gadgets Specification Discussion" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/85-e9fN... > .
> To post to this group, send email to
> opensocial-and-gadgets-spec@googlegroups.com.
> To unsubscribe from this group, send email to
> opensocial-and-gadgets-spec+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
On Thu, Jul 12, 2012 at 11:12 AM, drobin <drobin1...@gmail.com> wrote:
> Hi,
> Can someone help me understand the "REST-Query-Parameters" piece of the
> meta data incubating section in the Social API Specification ?
>>> ENCODE-REST-PARAMETERS(GetObjects-Request-Parameters)
> A code example would be helpful.
> For the /metadata/objects call, is the assumption that only a list of
> "object names" is returned ?
> Does Array<ObjectMetadata> contain something like [person, group,
> department] or does it contain
> [person{name, title}, group{owner, purpose}] for the most general version of
> this call ?
> How do the following calls differ from each other in what is returned ?
> /metadata/objects/person
> vs
> /metadata/properties/person
> The way the spec reads, it isn't clear that the following is not legal
> (I assume it is not) /metadata/objects/{field} Maybe it is splitting hairs,
> but it might be better
> to indicate that if {field} is supplied, the {name} parameter is not
> optional - unless the intent was
> to return all objects that implement {field} in which case {name} really is
> optional.
> What is the use case where someone would call the generic
> /metadata/properties call with no {name} ?
> Thanks !
> --
> You received this message because you are subscribed to the Google Groups
> "OpenSocial and Gadgets Specification Discussion" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/85-e9fN....
> To post to this group, send email to
> opensocial-and-gadgets-spec@googlegroups.com.
> To unsubscribe from this group, send email to
> opensocial-and-gadgets-spec+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
