... otherwise the example at http://schema.org/Person is not 100% correct as Geert-Jan notice on StackOverflow.
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.
Added URL as expected type of colleague (which sets JSON-LD context to …
See issue #929
Noted fix to #929 for colleague expecting URL values and @id in JSON-LD.
Implemented and queued for release, see http://webschemas.org/docs/jsonldcontext.json
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.
From: Dan Brickley [mailto:firstname.lastname@example.org]
Sent: Wednesday, March 09, 2016 5:50 AM
To: schemaorg/schemaorg email@example.com
Subject: Re: [schemaorg] Type-coerce "colleague" to @id in JSON-LD context (#929)
Reply to this email directly or view it on GitHub #929 (comment) . https://github.com/notifications/beacon/AKzkEeqL7iF65tEGOU4wjCv27IdBYmpFks5prrPPgaJpZM4G0Ids.gif