Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use term schema:encoding #139

Closed
tpluscode opened this issue Oct 4, 2022 · 2 comments
Closed

Cannot use term schema:encoding #139

tpluscode opened this issue Oct 4, 2022 · 2 comments

Comments

@tpluscode
Copy link
Contributor

I added the term https://schema.org/encoding to my mapping vocabulary. XRM does not like that and says

vocabulary schema {
  prefix "schema" "http://schema.org/"

  properties
    encoding
-   ^^^^^^^^
-   extraneous input 'encoding' expecting RULE_BLOCK_END(org.eclipse.xtext.diagnostics.Diagnostic.Syntax)
}

I tried escaping as "encoding" but then. I get 3 errors when used

map foo from bar {
  properties
    schema.encoding from bar
-   ^^^^^^^^^^^^^^^
-   Couldn't resolve reference to RdfProperty 'schema'.(org.eclipse.xtext.diagnostics.Diagnostic.Linking)
-   mismatched input 'encoding' expecting RULE_ID(org.eclipse.xtext.diagnostics.Diagnostic.Syntax)
}

As a workaround I added this weird extra vocab. Any better way?

vocabulary schemaen {
  prefix "schemaen" "http://schema.org/en"

  properties
    coding
}
@ktk
Copy link
Member

ktk commented Oct 4, 2022

See special identifiers and escaping, probably used within XRM itself.

@tpluscode
Copy link
Contributor Author

Of course, that was it. Thanks

@mchlrch mchlrch transferred this issue from zazuko/expressive-rdf-mapper Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants