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

Type-coerce "colleague" to @id in JSON-LD context #929

Closed
lanthaler opened this Issue Dec 12, 2015 · 3 comments

Comments

@lanthaler
Collaborator

lanthaler commented Dec 12, 2015

... otherwise the example at http://schema.org/Person is not 100% correct as Geert-Jan notice on StackOverflow.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 9, 2016

Contributor

Makes sense. I believe, given the way we do things currently, the way we'd express this would be adding URL as another expected type. And indeed the example under discussion is using URLs. Let's do that.

Contributor

danbri commented Mar 9, 2016

Makes sense. I believe, given the way we do things currently, the way we'd express this would be adding URL as another expected type. And indeed the example under discussion is using URLs. Let's do that.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 9, 2016

Contributor

Implemented and queued for release, see http://webschemas.org/docs/jsonldcontext.json

Contributor

danbri commented Mar 9, 2016

Implemented and queued for release, see http://webschemas.org/docs/jsonldcontext.json

@danbri danbri added this to the sdo-deimos release milestone Mar 9, 2016

@danbri danbri closed this Mar 9, 2016

@jaygray0919

This comment has been minimized.

Show comment
Hide comment
@jaygray0919

jaygray0919 Mar 9, 2016

Do you publish a change log of the differences between the current release and the planned release?

Here's the reason I ask:

We use a subset of the schema.org jsonldcontext.json statements in our @context declaration.

We also include other non-schema.org statements.

So, rather than using @vocab shema.org (and benefiting from updates to the vocab), we try to make the terms used in any document explicit.

Hence the desire to explicitly update existing documents with any vocab changes.

Thanks for guidance here.

/jay gray

From: Dan Brickley [mailto:notifications@github.com]
Sent: Wednesday, March 09, 2016 5:50 AM
To: schemaorg/schemaorg schemaorg@noreply.github.com
Subject: Re: [schemaorg] Type-coerce "colleague" to @id in JSON-LD context (#929)

Implemented and queued for release, see http://webschemas.org/docs/jsonldcontext.json


Reply to this email directly or view it on GitHub #929 (comment) . https://github.com/notifications/beacon/AKzkEeqL7iF65tEGOU4wjCv27IdBYmpFks5prrPPgaJpZM4G0Ids.gif

jaygray0919 commented Mar 9, 2016

Do you publish a change log of the differences between the current release and the planned release?

Here's the reason I ask:

We use a subset of the schema.org jsonldcontext.json statements in our @context declaration.

We also include other non-schema.org statements.

So, rather than using @vocab shema.org (and benefiting from updates to the vocab), we try to make the terms used in any document explicit.

Hence the desire to explicitly update existing documents with any vocab changes.

Thanks for guidance here.

/jay gray

From: Dan Brickley [mailto:notifications@github.com]
Sent: Wednesday, March 09, 2016 5:50 AM
To: schemaorg/schemaorg schemaorg@noreply.github.com
Subject: Re: [schemaorg] Type-coerce "colleague" to @id in JSON-LD context (#929)

Implemented and queued for release, see http://webschemas.org/docs/jsonldcontext.json


Reply to this email directly or view it on GitHub #929 (comment) . https://github.com/notifications/beacon/AKzkEeqL7iF65tEGOU4wjCv27IdBYmpFks5prrPPgaJpZM4G0Ids.gif

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