# Same resources with different attributes in different objects

**URL:** <https://discuss.jsonapi.org/t/same-resources-with-different-attributes-in-different-objects/1500>\
**Category:** Uncategorized\
**Created:** [February 4, 2019, 9:24pm UTC](https://discuss.jsonapi.org/t/same-resources-with-different-attributes-in-different-objects/1500 "2019-02-04T21:24:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![SpirIT](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/spirit/32/600_2.png) [@SpirIT](https://discuss.jsonapi.org/u/SpirIT)\
**Post date:** [February 7, 2019, 8:27am UTC](https://discuss.jsonapi.org/t/same-resources-with-different-attributes-in-different-objects/1500/4 "2019-02-07T08:27:12Z")

</div>

Hey,  
that product relation seems like a m:n relation with pivot data, right?

Shippings-Table {shipping\_id, …}  
Products-Table {shipping\_id, part\_id, qtyShipped, other-pivot-data}  
Parts-Table {part\_id}

I didn’t like it to put on the meta-tag, because actually its not meta-information.  
I’ve added the field “pivot” (outside of the specification)

```
"included": [
    {
      "type": "parts",
      "id": "10PIQPD3",
      "attributes": {
           "name": "Part PIQ PD3", ...
      },
      "pivot": {
          "partCondition": "F01",
          "qtyShipped": 1
      }, 
      links: { self: '/parts/10PIQPD3?shipping_id=1' }
    }
]

```

As well I populate the links with params, like here linking to an ID: shipping\_id

But actually while writing I’ve checked the specification, and I don’t know whether its good to do that?

Sorry, I think that was not to much help, but maybe it helps you for your project.

---

_[View the full topic](https://discuss.jsonapi.org/t/same-resources-with-different-attributes-in-different-objects/1500)._