Use of schema.org with hydra

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I want to mix Hydra with schema.org. I found that there is potential
for collisions and I am unsure how to solve them.

{
"@context": [
    "http://www.w3.org/ns/hydra/context.jsonld",
    {
      "@vocab" : "http://schema.org/"
    }
  ],
  "@type": "Movie",
  "description": "Jack Sparrow and Barbossa embark on a quest",
  "name": "Pirates of the Carribean",
  "operation": [
    {
      "@type": "DeleteResourceOperation",
      "method": "DELETE"
    }
  ]
}

When I run this through jsonld-java, I get:
{
  "@type" : "http://schema.org/Movie",
  "http://schema.org/name" : "Pirates of the Carribean",
  "http://www.w3.org/ns/hydra/core#description" : "Jack Sparrow and
Barbossa embark on a quest"
  "http://www.w3.org/ns/hydra/core#operation" : {
    "@type" : "http://schema.org/DeleteResourceOperation",
    "http://www.w3.org/ns/hydra/core#method" : "DELETE"
  }
}

IOW, hydra has hijacked the description attribute.

Would the solution be not to define
"http://www.w3.org/ns/hydra/context.jsonld" in the context, but only a
term hydra and apply hydra: to every single hydra term?

{
"@context":
    {
      "@vocab" : "http://schema.org/",
      "hydra": "http://www.w3.org/ns/hydra/core#",
    },
  "@type": "Movie",
  "description": "Jack Sparrow and Barbossa embark on a quest",
  "name": "Pirates of the Carribean",
  "hydra:operation": [
    {
      "@type": "DeleteResourceOperation",
      "hydra:method": "DELETE"
    }
  ]
}

If so, is it possible to point to hydra's external context file when
mixing with schema.org?

Best regards,
Dietrich
- -- 
Dietrich Schulten
Escalon System-Entwicklung

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iEYEARECAAYFAlP5jS8ACgkQuKLNitGfiZObYgCgzkMoLQ6PuOmMJuXTd/PKOfH2
HHwAn38jGgKWY9HNIy/qFAlpA6a7ryva
=c2T6
-----END PGP SIGNATURE-----

Received on Sunday, 24 August 2014 10:22:23 UTC