- From: tim duval <tim.duval11@gmail.com>
- Date: Mon, 3 Oct 2022 11:01:28 -0400
- To: public-n3-dev@w3.org
- Message-ID: <CAA8RyBhKNyWXCQ9SEBk0qs3qSNfmrS_nRx3om0oWGOGya1FiPw@mail.gmail.com>
I found that string:matches() looks like it can satisfy handling regular expressions Just the other two that I could use some help. On Mon, Oct 3, 2022 at 10:24 AM, tim duval <tim.duval11@gmail.com> wrote: > Hi! > > We are on the verge of implementing N3 for a product I am helping a client > develop and in their due diligence, they are providing me with challenges > to identify what the N3 equivalent is, e.g., Let's see if N3 can handle > this!! (suffice to say there is a little skepticism).... > > Most of the list is easy to handle, though a few of them stuck out to me > that it would be best to ask the community how these might be represented > in N3 (built-in wise): > > *Coalesce:* > Coalesce(@StatusCode,'123') > > *Regex expressions:* > how can regular expressions be used?? > e.g., substring('13.4 kv', '(([0-9]+.*)*[0-9]+)') as decimal --> returns > 13.4 > > *Convert time to current/provided timezone:* > > session-created-date-utc = "2022-08-15 18:57:40" > > current-timezone = 'CDT' > > result is: "2022-08-15 12:57:40" > > > Any help is appreciated > > > Thanks! > > > Tim Duval > > >
Received on Monday, 3 October 2022 15:01:52 UTC