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

map Person to vcard:Individual and remove as:Person #107

Closed
elf-pavlik opened this issue May 1, 2015 · 4 comments
Closed

map Person to vcard:Individual and remove as:Person #107

elf-pavlik opened this issue May 1, 2015 · 4 comments

Comments

@elf-pavlik
Copy link
Member

Similar to Organization, Person can map directly in JSON-LD context to vcard:Individual
http://www.w3.org/TR/vcard-rdf/#d4e1749

@jasnell unless you object I can prepare PR! I would also change this example http://www.w3.org/TR/2015/WD-activitystreams-core-20150129/#fig-an-actor-that-is-both-a-person-and-a-vcard-individual

seeAlso: w3c-social/social-vocab#11

@jasnell
Copy link
Collaborator

jasnell commented May 1, 2015

Hmm... that would introduce a normative dependency to VCard at the vocabulary level but that's really not too big of an issue. I would still want to map the "Person" term in the JSON-LD context, largely because of historical context, but "Person" would become deprecated in favor of "Individual". I have no particular issue with that but it should be brought up for a vote. "Person" has historical precedence within Activity Streams so we'll definitely want to get the community review.

@elf-pavlik
Copy link
Member Author

I thought about changing in context

{
  ...
  "Person": "vcard:Individual",
  ...
}

and remove http://www.w3.org/TR/activitystreams-vocabulary/#dfn-person all together just as you did remove http://www.w3.org/TR/activitystreams-vocabulary/#dfn-organization or leave it in just with vcard URI

actually while on it we could do just the same with Group

{
  ...
  "Group": "vcard:Group",
  ...
}

@jasnell
Copy link
Collaborator

jasnell commented May 1, 2015

If we did that, we'd want to explicitly mention that implementations need to treat vcard:Individual and vcard:Group as rdfs:subClassOf as:Actor. Then add equivalent statements to the non-normative vocabulary definition.

@jasnell
Copy link
Collaborator

jasnell commented May 7, 2015

Based on the WG decision to pull all external vocabularies from the AS 2.0 context, this issue no longer seems to be relevant. Closing.

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

3 participants