You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<graph> {:a :b :c}
is also directly valid in N3. Then we of course also need to fix the semantics.
Add a predicate to allow triple representation of named graphs in N3. Then we would have something like
<graph> :isNameFor {:a :b :c}
In that case it might be possible to add semantics to such triples by providing rule sets for the different existing semantics of named graphs. This of course depends on our solution for issue #8.
Ignore named graphs for now and maybe add them later.
What do you think?
The text was updated successfully, but these errors were encountered:
Both 1 and 2, where <graph> {:a :b :c} is shorthand syntax for <graph> :isNameFor {:a :b :c} or most common predicate, possibly :isNameFor, if you have one for all possible semantics.
I'd not ignore them because citing graphs is something people would turn to N3 for.
Is this something we still want to pursue, i.e., shorthand syntax for named graphs in N3, or defer this to a later point? Note that we have some ideas on how to support various named graphs semantics using N3 cited formulas, but distinguishing between them requires a predicate.
Related to #1
Which of the three options would you prefer:
<graph> {:a :b :c}
is also directly valid in N3. Then we of course also need to fix the semantics.
<graph> :isNameFor {:a :b :c}
In that case it might be possible to add semantics to such triples by providing rule sets for the different existing semantics of named graphs. This of course depends on our solution for issue #8.
What do you think?
The text was updated successfully, but these errors were encountered: