Skip to content

Notation3: Cannot parse Resource Paths #508

@tpluscode

Description

@tpluscode
Contributor

I use eye to process rules which use shorthand resource paths.

For example,

"Some message"^log:trace .

This would be equivalent to

[] log:trace "Some message" .

n3.js fails with error message Expected entity but got . on line 1.

Activity

changed the title [-]Notation3: Cannot parse Resource Paths used like an incomplete statement[/-] [+]Notation3: Cannot parse Resource Paths[/+] on Mar 10, 2025
tpluscode

tpluscode commented on Mar 10, 2025

@tpluscode
ContributorAuthor

Update: looks like resource paths are not supported at all?

jeswr

jeswr commented on Mar 10, 2025

@jeswr
Collaborator

Please see requested sanity check in #509

jeswr

jeswr commented on Mar 12, 2025

@jeswr
Collaborator

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

jimsmart commented on Mar 16, 2025

@jimsmart
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @tpluscode@jimsmart@jeswr

        Issue actions

          Notation3: Cannot parse Resource Paths · Issue #508 · rdfjs/N3.js