updated registry files

21 views
Skip to first unread message

James M Snell

unread,
Aug 30, 2012, 2:15:54 PM8/30/12
to activity...@googlegroups.com
I've gone through and updated the registry yaml files with the various new object types, verbs, external vocabs etc... the tools to generate the registry need to be updated, however, to account for the external vocabulary stuff. Unless someone else gets to it first, I will try to do that tomorrow.

- James

Martin Atkins

unread,
Aug 30, 2012, 2:25:40 PM8/30/12
to activity...@googlegroups.com
What exactly needs to be added for this?

If I understood the latest spec on this correctly, we've just defined a
property name for each of a set of external vocabularies, so from the
point of view of the registry wouldn't these just be declared as object
or activity components?

e.g.

- name: GeoJSON
description: GeoJSON object related to the object.
specification_anchor: geojson
json:
property_name: geojson
specification_anchor: geojson


James M Snell

unread,
Aug 30, 2012, 2:32:23 PM8/30/12
to activity...@googlegroups.com
Yeah, it could be done that way. In the yaml I have it separated out as a different section but it doesn't have to to be way.




--
You received this message because you are subscribed to the Google Groups "Activity Streams" group.
To post to this group, send email to activity-streams@googlegroups.com.
To unsubscribe from this group, send email to activity-streams+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/activity-streams?hl=en.


Martin Atkins

unread,
Aug 30, 2012, 2:40:03 PM8/30/12
to activity...@googlegroups.com
On 08/30/2012 11:32 AM, James M Snell wrote:
> Yeah, it could be done that way. In the yaml I have it separated out as
> a different section but it doesn't have to to be way.
>

The original motivation for the registry was to establish some
namespaces. Since object/activity components share the same namespace as
external vocabulary keys I think it's clearer to keep them together so
that there's a single place to look for "what keys are valid in this
context and what do they mean?"

The other principle under which the registry was designed is that it is
an index of specs rather than a replacement for them. In other words, it
shouldn't aim to capture all of the subtleties of the specs, it should
just provide minimal information to help recognize a particular element
and then link to the normative prose describing that element.


James M Snell

unread,
Aug 30, 2012, 2:54:47 PM8/30/12
to activity...@googlegroups.com
Ok, I've moved the external vocab stuff into the object and activities components sections.

Reply all
Reply to author
Forward
0 new messages