Re: editorial problem in example in 6.1

Looks good now.

peter

On 02/08/2017 05:01 PM, Holger Knublauch wrote:
> I have just added an additional CSS declaration that has fixed the line break
> issue on Windows 10 / EDGE browser. Could you kindly verify if it also works
> for you now? (On this occasion I also turned this particular single-quoted
> string into a """ string - it was a long expression indeed).
> 
> Thanks,
> Holger
> 
> 
> 
> On 8/02/2017 13:52, Peter F. Patel-Schneider wrote:
>> Although the actual character sequence in the string may not include a
>> newline, a browser may break the string on display, giving the appearance of
>> illegal syntax.
>>
>> It is probably better to use """ for all strings, even very short ones, just
>> so that there is no possibility of the appearance of illegality.
>>
>> peter
>>
>>
>> On 02/07/2017 07:49 PM, Holger Knublauch wrote:
>>> This parses OK for me. Are we talking about the same query:
>>>
>>> sh:PatternConstraintComponent
>>>      a sh:ConstraintComponent ;
>>>      sh:parameter [
>>>          sh:path sh:pattern ;
>>>      ] ;
>>>      sh:parameter [
>>>          sh:path sh:flags ;
>>>          sh:optional true ;
>>>      ] ;
>>>      sh:validator shimpl:hasPattern .
>>>
>>> shimpl:hasPattern
>>>      a sh:SPARQLAskValidator ;
>>>      sh:message "Value does not match pattern {$pattern}" ;
>>>      sh:ask "ASK { FILTER (!isBlank($value) && IF(bound($flags),
>>> regex(str($value), $pattern, $flags), regex(str($value), $pattern))) }" .
>>>
>>> Thanks,
>>> Holger
>>>
>>>
>>> On 8/02/2017 12:58, Peter F. Patel-Schneider wrote:
>>>> The example in 6.1 has what appears to be an incorrectly delimited multi-line
>>>> literal.
>>>>
>>>> Peter F. Patel-Schneider
>>>> Nuance Communications
>>>>
>>>
>

Received on Thursday, 9 February 2017 01:10:27 UTC