RE: Multiple @require in a single document

On Tuesday, July 08, 2014 4:29 PM, Nicholas Bollweg wrote:
> I was just dinking around with an interesting JSON format, JSON
> Resume: http://jsonresume.org/

It's always interesting to see how certain things go viral


> I put together this initial stab at a context for it, using schema.org
> terms: https://github.com/jsonresume/resume-schema/issues/42 (feel
> free to chime in there! how would you handle "bio"?

The question is what the top level object really represents. Is it the CV? Then mapping it to schema.org/about might work. Is it the person? Then a schema.org/sameAs is probably better.


> how about the mix of content in the "work"?

This might be a use case for schema.org/Role or schema.org/OrganizationRole


> Is there a non-intrusive way to inject @types?)

Nope unless you use rdfs:range/domain to do so


> Here is the bogus context applied to their sample resume.json:
> http://tinyurl.com/mdc6k63
> 
> One thing I noticed was about the "work" and "publications" terms,
> both of which use @reverse. Apparently, only the latest one is honored
> in expansion (or any of the features).

That appears to be a bug in jsonld.js. It works fine in my processor. My playground is here:

   http://www.markus-lanthaler.com/jsonld/playground/


> Here is a simpler playground version, based on the @reverse example
> from the spec: http://tinyurl.com/multiple-reverse

Thanks. I just added this to the test suite:

  https://github.com/json-ld/json-ld.org/commit/0e667a754788e536114dceda202f129392f770c0


> I would expect to also see #bart and #lisa as children under the pets.
> Any thoughts? Am I doing something glaringly wrong? Are there any
> examples of using multiple @reverse correctly?

No, you are completely right. This appears to be a bug in jsonld.js


--
Markus Lanthaler
@markuslanthaler

Received on Tuesday, 8 July 2014 16:13:36 UTC