@ericprud looking at https://shapetrees.org/TR/specification/index.html#shapetree-virtual
the object is a Literal. Once we run turtle parser and get RDFJS DatasetCore we will lose all the prefixes. How are we supposed to use that Shape Path once the prefixes are gone?
if we only do direct references, we only need the predicate
<#VirtualProjectTree> a st:ShapeTree ; st:expectsType st:Resource ; st:shape ex:ProjectShape ; st:references [ st:hasShapeTree <#VirtualMilestoneTree> ; st:viaShapePath "@ex:ProjectShape/ex:hasMilestone" ] .
ex:ProjectShapefrom 'the parent' anyways
<#VirtualProjectTree> a st:ShapeTree ; st:expectsType st:Resource ; st:shape ex:ProjectShape ; st:references [ st:hasShapeTree <#VirtualMilestoneTree> ; st:viaPredicate ex:hasMilestone ] .
ex:hasMilestonewould get properly expanded by the parser
InheritInstancesData Grant, I found very inconvenient how
ldp:containspoints to the resource and not its focus node. Actually I changed it to point to focus node https://github.com/solid/data-interoperability-panel/pull/130/files#diff-be21cbad4d5d3b9a5414aa3455ee8527d0d21ae6f0b625aecf1dab1688461281R14 but that's most likely incorrect use of
@elf-pavlik the outstanding PRs have been approved / merged
Thank you! @justinwb
AllInstancesseems straight forward and it can support creating new instances. How about:
SelectedInstances- would we want to ever support creating new instances with this scope?
InheritInstances- probably the most interesting since here we never go through the data registrations and always through parent data instances, also if parent is one of remote data grants we don't have a reference(s) for data registrations of children.
Hi @/all - given some movement and activity of late related to client/server notification protocols, the protocol editors have created an issue at solid/process#258 to gauge interest in re-establishing the notifications panel to advance proposals and implementation work:
Please see solid/process#258 and :+1: / :-1: / comment if you’re interested in participating.