- From: Jos De Roo <josderoo@gmail.com>
- Date: Mon, 3 Oct 2022 17:11:32 +0200
- To: tim duval <tim.duval11@gmail.com>
- Cc: public-n3-dev@w3.org
- Message-ID: <CAJbsTZdfZn4xMXKKDsSnC02c9BhFECRKnQwWn5u2zJB=Q7AKWA@mail.gmail.com>
Indeed and for reasoning with time we have https://www.w3.org/TR/rif-dtb/ implemented in eye see https://github.com/josd/eye/blob/master/reasoning/rif/rifP.n3 dunno what coalesce is, maybe something like in https://github.com/phochste/Notation3-By-Example/blob/main/string/concatenation.n3 ? Jos -- https://josd.github.io On Mon, Oct 3, 2022 at 5:02 PM tim duval <tim.duval11@gmail.com> wrote: > 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:11:57 UTC