-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow declaring @container
on @type
#122
Comments
We discussed that several times but so far we decided to not support that. I see a number of problems with this:
Is this just be a "nice-to-have" for you or is it preventing some use cases respectively requiring an excessive amount of client code that could otherwise be elminited? As I see it, it just requires one additional if-statement in the client application. |
From my perspective, allowing context to set a To be clear, I'm only advocating that contexts be allowed to assign On Thu, May 17, 2012 at 1:16 AM, Markus Lanthaler
|
Would a flag in the compaction algorithm be fine as well for you or does it absolutely need to go into the context? |
If I could pass a flag in the options to frame() and that flag makes it
|
Turtle would allow setting a rdf:type as a list; it doesn't make sense, but the syntax allows it. +1 to allow @container @set on @type |
Would it be a viable alternative to allow this just in framing and ignore it in all other algorithms? |
RESOLVED: Add a flag to the .compact() and frame.() algorithms that turns off optimization of arrays with single items in them to single values in the output. |
For consistent framing, I sometimes want to force an object's
@type
into an array. This would mean allowing a context like:... which currently throws a 'keywords cannot be overridden' error.
The text was updated successfully, but these errors were encountered: