# Ingesting edge properties via JSON-LD

**URL:** https://community.stardog.com/t/ingesting-edge-properties-via-json-ld/4338
**Category:** Bug
**Created:** [April 17, 2023, 5:24am UTC](https://community.stardog.com/t/ingesting-edge-properties-via-json-ld/4338 "2023-04-17T05:24:38Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![gmangiante](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/gmangiante/32/1720_2.png) [@gmangiante](https://community.stardog.com/u/gmangiante)
#### Post date: [April 17, 2023, 5:24am UTC](https://community.stardog.com/t/ingesting-edge-properties-via-json-ld/4338/1 "2023-04-17T05:24:38Z")

</div>

Hello-

This is a follow up to support topic [https://community.stardog.com/t/edge-property-example-error/2561](https://community.stardog.com/t/edge-property-example-error/2561), which appears to have been closed a while ago. I've come up against the exact same issue - trying to import a JSON-LD file via the HTTP API (or via the Studio Load Data function) that contains edge properties, into a database with "edge.properties" enabled, and am receiving the message "Could not parse JSONLD: invalid @id value: value of @id must be a string." Has there been any progress on this issue? If not, could you suggest an alternate import format that will support ingestion of edge properties? Thanks!

---

<div class="post-metadata">

### Author: ![arwesterinen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/arwesterinen/32/40_2.png) [@arwesterinen](https://community.stardog.com/u/arwesterinen)
#### Post date: [May 17, 2023, 4:54pm UTC](https://community.stardog.com/t/ingesting-edge-properties-via-json-ld/4338/2 "2023-05-17T16:54:45Z")

</div>

Would it be possible to define (and Stardog to parse) the JSON-LD using the JSON-LD-star approach ([JSON-LD-star](https://json-ld.github.io/json-ld-star/))?

Andrea
