The skeleton code currently uses a human-readable descriptor id to store the underlying dataset. A more robust solution would be to use something like a UUID and/or some other identification scheme that ROSE manages. This id must be the same between the canonical decriptor and potentially pushed down into the AdvancedClient. This should not preclude a user's ability to retrieve a human-readable descriptor for development and logging purposes.
The skeleton code currently uses a human-readable descriptor id to store the underlying dataset. A more robust solution would be to use something like a UUID and/or some other identification scheme that ROSE manages. This id must be the same between the canonical decriptor and potentially pushed down into the
AdvancedClient. This should not preclude a user's ability to retrieve a human-readable descriptor for development and logging purposes.