Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

where's the "post" verb in the vocabulary? #37

Closed
dret opened this issue Oct 22, 2014 · 8 comments
Closed

where's the "post" verb in the vocabulary? #37

dret opened this issue Oct 22, 2014 · 8 comments

Comments

@dret
Copy link
Member

dret commented Oct 22, 2014

maybe i am reading the tables wrong, but shouldn't http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams2-vocabulary.html#dfn-verb say that there is a "post" very defined by the spec itself (and that all other verb values MUST be URIs)?

@jasnell
Copy link
Collaborator

jasnell commented Oct 22, 2014

Possibly. That's not clear tho. "post" doesn't actually belong to a vocabulary, it's just a simple identifier. We need to figure out how to best handle the legacy AS1 simple token identifiers like "post".

@dret
Copy link
Member Author

dret commented Oct 22, 2014

i agree that handling the string-only identifiers is important, but i think saying that they are "not part of a vocabulary" is a bit unintuitive. they may be the "legacy" or "built-in" or whatever-else vocabulary, but implementers should know about them, so they are part of the vocabulary that they need to support.

@jasnell
Copy link
Collaborator

jasnell commented Oct 23, 2014

What I've been considering is the definition of a "Legacy Vocabulary"... an
additional JSON-LD @context that maps the AS1 objectType and verb terms to
a URI namespace. Use of the additional @context would be optional and
separate from the main AS2 @context.

On Wed Oct 22 2014 at 4:42:37 PM Erik Wilde notifications@github.com
wrote:

i agree that handling the string-only identifiers is important, but i
think saying that they are "not part of a vocabulary" is a bit unintuitive.
they may be the "legacy" or "built-in" or whatever-else vocabulary, but
implementers should know about them, so they are part of the vocabulary
that they need to support.


Reply to this email directly or view it on GitHub
#37 (comment)
.

@dret
Copy link
Member Author

dret commented Oct 23, 2014

that sounds reasonable to me. it just would be good to have an easy way of finding out about the basic terms one has to understand in a basic implementation. in IETF-land, that would probably be a registry which still seems like the most sensible approach to me. any chance we can even have registries in W3C-land? i'd be more than happy to help to add this piece of robustness to the specs.

@elf-pavlik
Copy link
Member

@dret FYI

also http://activitystrea.ms/head/activity-schema.html#verbs - Activity Base Schema (Draft) - includes some verbs
last but not least maybe discussion with schema.org during TPAC could offer solution for vocabulary of 'verbs' or action/activity types and open 'registry'
https://www.w3.org/wiki/TPAC2014/SessionIdeas#Schema.org_and_Social_WG

@elf-pavlik
Copy link
Member

this one has even more verbs: http://activitystrea.ms/specs/json/schema/activity-schema.html#verbs

@jasnell
Copy link
Collaborator

jasnell commented Oct 25, 2014

And object types... the most recent version of the base schema document is hosted here: https://github.com/activitystreams/activity-schema/blob/master/activity-schema.md .. my plan is to write up a Note that proposes a way of handling these "legacy" verb and objectTypes.

@jasnell
Copy link
Collaborator

jasnell commented Dec 4, 2014

Covered by proposed "Extended Vocabulary"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants