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.

Sign up for GitHub

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

Jump to bottom

Move the entity name API from the SRE to the general API. #972

Closed
gallandarakhneorg opened this issue Feb 17, 2020 · 0 comments
Closed

Move the entity name API from the SRE to the general API. #972

gallandarakhneorg opened this issue Feb 17, 2020 · 0 comments
Assignees
@gallandarakhneorg
Labels
2 - In progress enhancement SARL API SARL Runtime Environment
Milestone
0.12.0

Comments

@gallandarakhneorg
Copy link
Member

gallandarakhneorg commented Feb 17, 2020 •
edited
Loading

The SRE implementation contains tools for naming objects (agents, behaviors, etc.) through a string of characters or an URI.

This naming API is almost independent of the SRE implementation itself.

The question that is arising is: should the naming API be moved from the SRE project to the general API?

If yes, is the moved code put inside a new project named io.sarl.naming or not?
@gallandarakhneorg gallandarakhneorg added this to the 0.11.0 milestone Feb 17, 2020
@gallandarakhneorg gallandarakhneorg modified the milestones: 0.11.0, 0.12.0 Feb 28, 2020
@gallandarakhneorg gallandarakhneorg self-assigned this Aug 18, 2020
gallandarakhneorg added a commit that referenced this issue Aug 20, 2020
@gallandarakhneorg
[api][sre] Move the naming API from Janus to the general SARL API.
596873b 
see #972

Signed-off-by: Stéphane Galland <galland@arakhne.org>
gallandarakhneorg added a commit that referenced this issue Aug 21, 2020
@gallandarakhneorg
[api][naming] Remove the NameScheme enumeration in order to enable sc…
bfc9c5b 
…heme support extensions.

see #972

Signed-off-by: Stéphane Galland <galland@arakhne.org>
gallandarakhneorg added a commit that referenced this issue Aug 21, 2020
@gallandarakhneorg
[api][naming] Add right management for access to named fields.
3f302c0 
The access right could be specified with annotations or by implementing
a dedicated agent skill.

see #972

Signed-off-by: Stéphane Galland <galland@arakhne.org>
gallandarakhneorg added a commit that referenced this issue Aug 21, 2020
@gallandarakhneorg
[api][naming] Reserve the "artifact" scheme for further usage.
331089b 
see #972

Signed-off-by: Stéphane Galland <galland@arakhne.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gallandarakhneorg gallandarakhneorg

Labels
2 - In progress enhancement SARL API SARL Runtime Environment
Projects
None yet
Milestone
0.12.0
Development

No branches or pull requests
1 participant
@gallandarakhneorg