You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
changed the title [-]Notation3: Cannot parse Resource Paths used like an incomplete statement[/-][+]Notation3: Cannot parse Resource Paths[/+]on Mar 10, 2025
If anyone is looking to pick this up - I'm fairly sure paths are supported but buggy on some cases such as lists. There was work some work done to fix this in #341, specifically be1bcd9
paths are supported but buggy on some cases such as lists.
Yeah, I seem to recall that currently N3Parser has paths working fine for IRIs/prefixed names, but - as you say - they're not currently implemented after lists... and also not after literals. (I have recently ported some of the N3.js code, so some of it is still fairly fresh in my memory)
This might be due to Notation3 spec changes since the original implementation of N3Parser's N3 support? Although I seem to recall previous specs were somewhat inexact in places, so it's difficult to be certain. It may just have been overlooked.
Activity
[-]Notation3: Cannot parse Resource Paths used like an incomplete statement[/-][+]Notation3: Cannot parse Resource Paths[/+]tpluscode commentedon Mar 10, 2025
Update: looks like resource paths are not supported at all?
jeswr commentedon Mar 10, 2025
Please see requested sanity check in #509
jeswr commentedon Mar 12, 2025
If anyone is looking to pick this up - I'm fairly sure paths are supported but buggy on some cases such as lists. There was work some work done to fix this in #341, specifically be1bcd9
jimsmart commentedon Mar 16, 2025
Yeah, I seem to recall that currently N3Parser has paths working fine for IRIs/prefixed names, but - as you say - they're not currently implemented after lists... and also not after literals. (I have recently ported some of the N3.js code, so some of it is still fairly fresh in my memory)
This might be due to Notation3 spec changes since the original implementation of N3Parser's N3 support? Although I seem to recall previous specs were somewhat inexact in places, so it's difficult to be certain. It may just have been overlooked.