VladimirAlexiev commented on issue #2851:
URL: https://github.com/apache/jena/issues/2851#issuecomment-2488434967

   @afs I'm looking at 
https://rawgit2.com/VladimirAlexiev/shacl/shaclc-grammars/shacl-compact-syntax/grammar/shaclc-ANTLR.html#constraint:
   - `nodeShape` has multiple constraints, separated by `.`
   - each constraint can be a `propertyShape`
   - `propertyShape` consists of a `path` followed by multiple `propertyAtoms`
   - `propertyAtom` can be `propertyValue`, which includes `message, 
minInclusive` etc
   
   So indeed PropertyShapes are expressed as a `.` separated sequence,
   but `path` should come first, and there should be only one `.` per path.
   
   I think the SHACLC should look like this. It would be nice to use some 
newlines and identations to emphasize the nesting:
   ```
    {
       cim:GovGAST3.tac
         minInclusive="0.0"^^xsd:float
         message="The value is negative." .
       cim:GovGAST3.tc
         minInclusive="0.0"^^xsd:float
         message="The value is negative." .
       cim:GovGAST3.td
         minInclusive="0.0"^^xsd:float
         message="The value is negative." .
       cim:GovGAST3.tg
         minInclusive="0.0"^^xsd:float
         message="The value is negative." .
       cim:GovGAST3.tsi
         minInclusive="0.0"^^xsd:float
         message="The value is negative." .
       cim:GovGAST3.ttc
         minInclusive="0.0"^^xsd:float
         message="The value is negative." .
       cim:GovGAST3.ty
         minInclusive="0.0"^^xsd:float
         message="The value is negative." .
   }
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to