Why specify URI's to objects?

XMLWordPrintable

    • Type: Bug
    • Resolution: Applied
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      1. remove URI property
      2. remove contentStreamUri property

      Show
      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?

            Assignee:
            Ryan McVeigh (Inactive)
            Reporter:
            Ryan McVeigh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: