- From: Peter F. Patel-Schneider via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Mar 2018 17:32:56 +0000
- To: public-shex-dev@w3.org
Better would be something that clears up whether Section 4 is operational. If operational it should say something about "add" instead of "has" and explictly not add if that would cause a duplicate. If not operational it should say that the fixed ShapeMap has only the shape associations sanctioned by the section. Right now the section is neither fish nor fowl. One could easily read the note as saying that if a duplicate is produced then the query ShapeMap cannot be converted to a fixed ShapeMap for the graph in question. peter On 3/14/18 1:24 PM, ericprud wrote: > > I added a note > <http://shexspec.github.io/shape-map/#query-to-fixed-set> so as to not > imply this was a new constraint. This is the first 2119 keyword in the > document. > > Note that though <a>shape associations</a> with triple patterns may imply redundant fixed ShapeMap associations, the combination of node and shape in the fixed map MUST be unique. > > If that address this issue, feel free to close it. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/shexSpec/shape-map/issues/14#issuecomment-373105904>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AGT8e1t_NESM1Yoe9PGZoYiVN67fudLMks5teVI_gaJpZM4SosyK>. > -- GitHub Notification of comment by pfps Please view or discuss this issue at https://github.com/shexSpec/shape-map/issues/14#issuecomment-373108973 using your GitHub account
Received on Wednesday, 14 March 2018 17:32:59 UTC