Skip to content

Native RDF representation and Namespacing #3

Open
@DiegoPino

Description

@DiegoPino

All operations on RDF will be managed internally as JSON-LD documents
For portability and normalization needs all JSON-LD documents will be assumed and handled internally as expanded contextless. (FULL URL)
There won't be XSD guessing but JSON-LD native types will be preserved

No namespacing will be stored per Resource and @context will be swappable if needed.
Multiple @graphs will be used to keep server managed RDF/ User managed RDF in separate domains but same serialized Document.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions