iridiankin

I encountered the same error. For my own issue the superficial workaround was to add an explicit `DependsOn` directive from my `AWS::Serverless::API` resource to all `AWS::Serverless::Function` resources that were referred...

> It seems to me that your proposal aims at breaking the principle of [URI opacity](https://www.w3.org/TR/webarch/#uri-opacity). More precisely, what you are trying to say is "_any_ IRI starting with `xyz`,...

> I disagree that the URI/IRI opacity argument is limited to example 1. Both example imply that anybody can coin a new IRI with a given prefix (`s:` in example...

As an addendum: I would also be looking for a way to specify that node dict key "s:foo#bar" would also imply "s:foo#bar a s:foo"; whether explicitly, structurally via JSON-LD @context,...

I did a bit of analysis to help myself conseptualize the process more clearly, as I wanted to find an answer to the question "Do I want to 'cook'?" and...

> To attempt to summarize from my understanding, the request is to allow per prefix defaults to be set, such as for `@container`. Thus setting `@container:@list` on `dc` would make...

> > I would also be looking for a way to specify that node dict key "s:foo#bar" would also imply "s:foo#bar a s:foo"; whether explicitly, structurally via JSON-LD @context, or...

> This could be discussed in the JSON-LD community group towards a solution for a future version, and we will keep it in mind for inclusion if it solves bugs...