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

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

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

@danbri danbri was assigned by RichardWallis Mar 7, 2016
@danbri
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 danbri pushed a commit that referenced this issue Mar 9, 2016
Dan Brickley Added URL as expected type of colleague (which sets JSON-LD context to
…@id too).

See issue #929
08f3299
@danbri danbri pushed a commit that referenced this issue Mar 9, 2016
Dan Brickley Noted fix to #929 for colleague expecting URL values and @id in JSON-LD. 3b40415
@danbri
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

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