Monday, 31 October 2016
- Re: ISSUE-140: Suggestion to close
- Re: ISSUE-140: Suggestion to close
- Re: ISSUE-158: Request to review change
- Re: ISSUE-158: Request to review change
- Re: ISSUE-140: Suggestion to close
- Re: ISSUE-140: Suggestion to close
- Re: ISSUE-140: Suggestion to close
- Re: ISSUE-140: Suggestion to close
- ISSUE-158: Request to review change
Sunday, 30 October 2016
Friday, 28 October 2016
- Re: shapes-ISSUE-192 (Are filters shapes?) - final questions
- Re: shapes-ISSUE-192 (Are filters shapes?) - final questions
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
Thursday, 27 October 2016
- shapes-ISSUE-193 (Focus nodes): Targets can be refined; focus nodes do not change
- RDF Data Shapes WG minutes for 26 October 2016
- Meeting time slot and daylight shifting
Wednesday, 26 October 2016
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- Re: sh:in vs. sh:value
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- Re: ISSUE-140: Suggestion to close
- RE: RDF Data Shapes WG agenda for 26 October 2016
- Re: sh:in vs. sh:value
- sh:in vs. sh:value
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- RDF Data Shapes WG agenda for 26 October 2016
Tuesday, 25 October 2016
- Re: Stem difference between ShEx and SHACL
- Stem difference between ShEx and SHACL
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
Monday, 24 October 2016
Friday, 21 October 2016
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
Thursday, 20 October 2016
- RDF Data Shapes WG Virtual F2F poll
- Sample comments
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- proposal to close issues related to sh:hasShape
- RDF Data Shapes WG minutes for 19 October 2016
Wednesday, 19 October 2016
- Re: shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- shapes-ISSUE-192 (Are focus nodes shapes?): Should focus nodes be of type sh:Shape? if not, then what?
- Re: shapes-ACTION-43: Take a read through the spec and raise specific terminology issues as needed
- Re: an alternative proposal for partition
- Re: shapes-ISSUE-191 (Parameter value types): Should the value types of parameters be constraints [SHACL Spec]
Tuesday, 18 October 2016
- Re: shapes-ISSUE-191 (Parameter value types): Should the value types of parameters be constraints [SHACL Spec]
- Re: RDF Data Shapes WG agenda for 19 October 2016
- Re: shapes-ISSUE-191 (Parameter value types): Should the value types of parameters be constraints [SHACL Spec]
- RDF Data Shapes WG agenda for 19 October 2016
- RDF Data Shapes WG Minutes for 11 October 2016
- shapes-ISSUE-191 (Parameter value types): Should the value types of parameters be constraints [SHACL Spec]
- Re: FW: shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- Re: FW: shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- Re: shapes-ACTION-43: Take a read through the spec and raise specific terminology issues as needed
- ISSUE-92: sh:partition
- Re: shapes-ACTION-43: Take a read through the spec and raise specific terminology issues as needed
Monday, 17 October 2016
- Re: shapes-ACTION-43: Take a read through the spec and raise specific terminology issues as needed
- Re: shapes-ACTION-43: Take a read through the spec and raise specific terminology issues as needed
- FW: shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- Re: shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- Re: shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- Re: shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- Re: shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- Re: shapes-ISSUE-184 (paths & value nodes): Property paths and value nodes [SHACL - Core]
Sunday, 16 October 2016
Saturday, 15 October 2016
Friday, 14 October 2016
- Meeting days
- Re: Decomposing shapes
- Re: Decomposing shapes
- Re: Decomposing shapes
- Re: Decomposing shapes
- Re: Decomposing shapes
- Re: shapes-ISSUE-190 (Shape identification): Identifying the shapes in a SHACL Full shapes graph [SHACL - SPARQL]
Thursday, 13 October 2016
- Re: Decomposing shapes
- Re: optional features (was Re: ISSUE-131: Proposal to close)
- Re: optional features (was Re: ISSUE-131: Proposal to close)
- Re: ISSUE-131: Proposal to close
- Re: Decomposing shapes
- Re: shapes-ISSUE-190 (Shape identification): Identifying the shapes in a SHACL Full shapes graph [SHACL - SPARQL]
- Re: Decomposing shapes
- Decomposing shapes
- Re: shapes-ISSUE-190 (Shape identification): Identifying the shapes in a SHACL Full shapes graph [SHACL - SPARQL]
- Re: ISSUE-131: Proposal to close
- Re: shapes-ISSUE-190 (Shape identification): Identifying the shapes in a SHACL Full shapes graph [SHACL - SPARQL]
- Re: ISSUE-131: Proposal to close
- shapes-ISSUE-190 (Shape identification): Identifying the shapes in a SHACL Full shapes graph [SHACL - SPARQL]
- Re: ISSUE-131: Proposal to close
- Re: ISSUE-131: Proposal to close
- Re: ISSUE-131: Proposal to close
- Re: ISSUE-131: Proposal to close
- Re: ISSUE-131: Proposal to close
- Re: ISSUE-131: Proposal to close
- ISSUE-131: Proposal to close
Wednesday, 12 October 2016
Tuesday, 11 October 2016
- Re: shapes-ISSUE-178 (sh:message constraints): Should sh:message be permitted at constraints, too? [SHACL - Core]
- Re: shapes-ISSUE-178 (sh:message constraints): Should sh:message be permitted at constraints, too? [SHACL - Core]
- Re: shapes-ISSUE-178 (sh:message constraints): Should sh:message be permitted at constraints, too? [SHACL - Core]
- Invalid is undefined Re: shapes-ISSUE-183
- Re: shapes-ISSUE-178 (sh:message constraints): Should sh:message be permitted at constraints, too? [SHACL - Core]
- Re: shapes-ISSUE-183 (undefined term): Eliminating the term "Undefined" [SHACL - SPARQL]
Monday, 10 October 2016
- Action: format comments page as table - done
- Re: shapes-ISSUE-183 (undefined term): Eliminating the term "Undefined" [SHACL - SPARQL]
- RDF Data Shapes WG Minutes for 4 October 2016
- RDF Data Shapes WG agenda for 11 October 2016
- Re: shapes-ISSUE-178 (sh:message constraints): Should sh:message be permitted at constraints, too? [SHACL - Core]
- Re: shapes-ISSUE-187 (severity and message): sh:severity and sh:message are not defined as shapes graph properties
- Re: shapes-ISSUE-187 (severity and message): sh:severity and sh:message are not defined as shapes graph properties
- Re: shapes-ISSUE-187 (severity and message): sh:severity and sh:message are not defined as shapes graph properties
Sunday, 9 October 2016
- Re: shapes-ISSUE-187 (severity and message): sh:severity and sh:message are not defined as shapes graph properties
- Re: shapes-ISSUE-186 (validaton report properties): Properties in validation report mis-use shapes graph properties
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- shapes-ISSUE-189 (validation trigger): Clarify validation report trigger in section 3
- shapes-ISSUE-188 (define validation): "Validation" needs to be defined
- shapes-ISSUE-187 (severity and message): sh:severity and sh:message are not defined as shapes graph properties
- shapes-ISSUE-186 (validaton report properties): Properties in validation report mis-use shapes graph properties
Saturday, 8 October 2016
Friday, 7 October 2016
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- Re: ISSUE-140: Suggestion to close
Thursday, 6 October 2016
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- ISSUE-93 and ISSUE-94 (attn: Harold)
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
- Re: shapes-ISSUE-182 (Validation report): [Editorial] Clarifications need to section 3.0
Wednesday, 5 October 2016
- Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec])
- Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec])
Tuesday, 4 October 2016
- Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec])
- apologies
- Re: "property values"
- Re: "property values"
- Re: RDF Data Shapes WG agenda for 4 October 2016
Monday, 3 October 2016
- "property values"
- Re: Terminology section restructuring
- RDF Data Shapes WG agenda for 4 October 2016
- Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec])
- Re: Terminology section restructuring
- Terminology section restructuring
- Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]
- Re: Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec])
Sunday, 2 October 2016
- Node vs focus node (Was: Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec])
- Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]
- shapes-ISSUE-185 (processing order): Processing order for filters and constraints [SHACL - Core]
- Re: shapes-ISSUE-181: SHACL conformance for partial validation reports [SHACL Spec]
- shapes-ISSUE-184 (paths & value nodes): Property paths and value nodes [SHACL - Core]
- shapes-ISSUE-183 (undefined term): Eliminating the term "Undefined" [SHACL - SPARQL]
- Re: Declare and define