In the discussion around allowing id-maps for values patterns, I discovered that we don't actually support IRIs in value maps for regular processing - only as special value-pattern syntax.
This PR adds support for that style of IRI ref construction. I could have added support for IRIs in value-maps to the json-ld library, but that is not how expand works according to the json-ld spec. Since this is a proprietary extension I chose to implement it db, though, since our json-ld processor library is not a compliant processor, we could sneak it there if we'd like.
I also had to re-work the annotation validation logic to detect references that are represented with value maps.
In the discussion around allowing id-maps for values patterns, I discovered that we don't actually support IRIs in value maps for regular processing - only as special value-pattern syntax.
This PR adds support for that style of IRI ref construction. I could have added support for IRIs in value-maps to the json-ld library, but that is not how
expandworks according to the json-ld spec. Since this is a proprietary extension I chose to implement itdb, though, since our json-ld processor library is not a compliant processor, we could sneak it there if we'd like.I also had to re-work the annotation validation logic to detect references that are represented with value maps.