Skip to content

Slot id on class Entity is not required #83

@eecavanna

Description

@eecavanna

When looking at the schema docs yesterday, I noticed the id slot on the Entity class was not required.

Image

I looked at the YAML source code and saw # required: true is commented out.

id:
aliases:
- BER data source internal identifier
- CURIE
description: The unique ID used for the entity within the BER resource. It may not necessarily be resolvable outside the resource.
comments:
- If the data source does not use CURIEs, we cannot guarantee that IDs will be unique between all the BER sources.
# identifier: true
# required: true
range: string
slot_uri: schema:identifier

I discussed this with @shreddd and he mentioned that the JSON-to-Mongo ingester is implemented under the assumption that each entity has an id.

I think there is an inconsistency in our system here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions