-
Notifications
You must be signed in to change notification settings - Fork 23
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
Should network resources' occi.core.id contain "/network/" part? #33
Comments
occi.core.id's structure is opaque, so long as it is unique within the domain of the service provider, so I'd agree with what you say @bhagemeier. If it is unclear from the spec then I'd suggest we continue the conversation on the OCCI ML. |
You are, of course, right. There are almost no restrictions on At the moment It's difficult to implement a reasonably human-readable output formatting (or provide a user-friendly interface) when there are structure changes not only from implementation to implementation but also from resource to resource in one implementation. This, of course, has no effect on functionality but it's not always easy to explain to users why sometimes they can write
and see the last part of the location matching the ID and sometimes have an ID and not be able to write
to get some more information about the resource. Am I completely wrong? |
IMO, from an implementation consistency point of view you're correct. |
@dizz, should we resolve this issue somehow? A dangling question is never a good idea. Should this become a feature request? I had a brief look at the code, but I'm not quite sure whether I would get it right. |
Have set it as an enhancement. If you could suggest a pull request that would be highly appreciated. Likely that at this point is a good start |
Hi,
I've been pointed to this issue about the occi.core.id. @arax is of the opinion that it should not, but I cannot see anything in the core OCCI spec that would restrict the id. After all, it is a URI w/o semantics. Let's clarify this.
Björn
The text was updated successfully, but these errors were encountered: