|
If you were logged in you would be able to see more operations.
|
|
|
| Proposal: |
1. remove URI property
2. remove contentStreamUri property
1. remove URI property
2. remove contentStreamUri property
|
|
0.62a Domain Model lines 169, 986, 1044, 1090, 1137
What is the point of specifying a URI to an object when it has no expected (usable by a client) behavior or semantics? A repository can create a property for this purpose if it wishes, and it will make just as much sense to a client. As this is not useful to a client, can it be removed from the spec?
|
|
Description
|
0.62a Domain Model lines 169, 986, 1044, 1090, 1137
What is the point of specifying a URI to an object when it has no expected (usable by a client) behavior or semantics? A repository can create a property for this purpose if it wishes, and it will make just as much sense to a client. As this is not useful to a client, can it be removed from the spec? |
Show » |
|
Bug
Closed
Major
Why specify URI's to objects?