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

Choose prefix character to replace @ #55

Closed
anatoly-scherbakov opened this issue Jul 7, 2022 · 2 comments
Closed

Choose prefix character to replace @ #55

anatoly-scherbakov opened this issue Jul 7, 2022 · 2 comments
Labels
UCR Issue on Use Case/Recommendation wontfix This will not be worked on

Comments

@anatoly-scherbakov
Copy link
Contributor

anatoly-scherbakov commented Jul 7, 2022

As an architect of a YAML-LD aware system and a developer, I am a bit uncomfortable about having my users write JSON-LD @-keywords and have to quote them because that would mean additional effort. I would rather prefer some other prefix character from ASCII character set.

Choice of prefix characters

@id Notes Resolution
@id Is reserved. x
`id Is reserved. x
~id Works
!id Used for tags x
#id Used for comments x
$id Works x
%id Used for directives x
^id Works
&id Used for anchors x
*id Used for aliases x
-id Works, but is confusable with lists: - id x
+id Works
_id Works but is confusable with blank nodes (#57) x

Also, _ in Python means private or internal things so I am subconsciously against that :)

I suggest using $ for the Convenience Context. This character also is good for JS: something.$type is workable in that language.

The users however may do whatever they want. For instance, users might want something like this:

=: 🏠:cat
: 🐱
🏷️:
  🇺🇸: Ray

I won't stop them. Our $ is really just a way to trigger everyone's imagination.

@VladimirAlexiev
Copy link
Contributor

A good analysis what chars are suitable for #51

@gkellogg
Copy link
Member

Discussed in the TPAC F2F and resolved to close as won't fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UCR Issue on Use Case/Recommendation wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants