Skip to content

Context prefixes not supported? #124

@Ostrzyciel

Description

@Ostrzyciel

Hi! First of all, thank you for the hard work on this! ❤

I'm more from the RDF world, so I wanted to try this out with typical RDF data (sample). Following the @prefix directives from the sample, I defined this context for JSON-LD compaction:

{
  "@context": {
    "aiot": "https://assist-iot.eu/ontologies/aiot#",
    "aiot_p2": "https://assist-iot.eu/ontologies/aiot_p2#",
    "geosparql": "http://www.opengis.net/ont/geosparql#",
    "om": "http://www.ontology-of-units-of-measure.org/resource/om-2/",
    "pilot": "https://assist-iot.eu/pilot2_rdf/",
    "prov": "http://www.w3.org/ns/prov#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "sosa": "http://www.w3.org/ns/sosa/",
    "ssn": "http://www.w3.org/ns/ssn/",
    "xsd": "http://www.w3.org/2001/XMLSchema#"
  }
}

(I'm not very familiar with JSON-LD, and the above is what Jena would do, and Jena is often smart, so I follow that)

While I can compact this with Titanium, I do get a com.apicatalog.cborld.encoder.EncoderError: Non compress-able document. exception with Iridium. It seems to be coming from this method that doesn't implement a case for when the context is a map with multiple entries.

Full reproduction code: https://github.com/Ostrzyciel/jelly-cbor-ld

I just have no idea if this is a limitation of CBOR-LD or Iridium, and what is the recommended approach here. I also don't want to hand-craft contexts, because I have no idea what kind of data I will be processing.

Please bear with me if this question doesn't make sense, I do admittedly have little understanding of CBOR-LD 😄

Sub-issues

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