Default value for @type

[AtesComp]

Currently, @type cannot accept @default in the playground. For framing, the documentation seems to indicate that @type (a keyword) must be a definitive resource for matching and not definable.

So, how is type added via framing?

I assume the answer would be either:

1. "@type": {"@default": "ex:Book"}
2. "@type": {"@default": {"@id": "ex:Book"}}

Since "@type": "@id" is the usual specification, 2 seems redundant.

NOTE: I know, I've bugged about this quite a bit in the main JSON-LD area. Since framing was proposed as the solution, I'm officially posting the issue here.

[gkellogg]

Yes, we did say that framing was the right way to do this, but the framing algorithm doesn't presently allow for this.

Defaults are added in 4.7.4 of the Framing Algorithm which iterates over non-keywords, and thus ignores a default for @type. It is probably sufficient to update the algorithm to also include @type.

[iherman]

This issue was discussed in a meeting.

• RESOLVED: Accept framing #74 as an oversight to be fixed for <code>@type</code> on node objects
  View the transcript

  @default for @type
  Rob Sanderson: https://github.com/w3c/json-ld-framing/issues/74
  Rob Sanderson: The only thing you can’t consider @default for is @type.
  Gregg Kellogg: Also not @id.
  … Framing was mentioned as the proper way to handle these cases, but it does not work right now.
  Rob Sanderson: This fits with our general pattern to allow @type to allow more functionality and context, such as @container and @set.
  … While our feature window is closed, we can consider this a bug.
  Dave Longley: This is indeed an oversight, something we can fix.
  Pierre-Antoine Champin: So the idea is that @type with @default would set the type on node object or value objects, or any of them?
  Gregg Kellogg: I think only on node objects.
  … We would have to check the algorithm.
  Dave Longley: I think gkellogg is correct.
  Rob Sanderson: Me too. Otherwise we would open up weird issues with @direction and @value.
  Dave Longley: +1 to azaroth
  Proposed resolution: Accept framing #74 as an oversight to be fixed for @type on node objects (Rob Sanderson)
  Gregg Kellogg: +1
  Jeff Mixter: +1
  Rob Sanderson: +1
  Ruben Taelman: +1
  Dave Longley: +1
  Pierre-Antoine Champin: +1
  Ivan Herman: +1
  Resolution #4: Accept framing #74 as an oversight to be fixed for @type on node objects
  

[azaroth42]

Resolved, closing :)