Skip to content

Should we recommend @type? #2

@stain

Description

@stain

JSON-LD style is often light-weight, relying on properties and domain/ranges, and don't usually pepper @type on objects which type is already given by their properties.

However, @type makes it easier to execute SPARQL queries without having to do OWL reasoning or reflecting the whole object structure in SPARQL.

So should we keep this part of section 2?

The @type SHOULD be provided for ORE resources of type Aggregation, ResourceMap, Proxy, and MAY be provided for resources of type AggregatedResource and others.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions