Deprecate use of resource type LocalResource. Replace with AnyResource with a representation of Inline.

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: Major
    • Component/s: None
    • None
    • Hide

      OSLC deprecate use of resource type LocalResource. In all Core shapes, LocalResource shall be replaced with AnyResource with a representation of Inline. The TC believes this change is backward-compatible, and recommends that all domains make the same change to shapes.

      Show
      OSLC deprecate use of resource type LocalResource. In all Core shapes, LocalResource shall be replaced with AnyResource with a representation of Inline. The TC believes this change is backward-compatible, and recommends that all domains make the same change to shapes.
    • Hide

      OSLC deprecate use of resource type LocalResource. In all Core shapes, LocalResource shall be replaced with AnyResource with a representation of Inline. The TC believes this change is backward-compatible, and recommends that all domains make the same change to shapes. - TC voted to accept this on 1st Oct 2015

      Show
      OSLC deprecate use of resource type LocalResource. In all Core shapes, LocalResource shall be replaced with AnyResource with a representation of Inline. The TC believes this change is backward-compatible, and recommends that all domains make the same change to shapes. - TC voted to accept this on 1st Oct 2015

      See "proposal". Also, see discussion in OSLCCORE-35 and in TC meeting 1st Oct 2015.

      The key problem is that, i a resource shape, oslc:valueType of oslc:LocalResource requires a blank node. However, turning Service Providers into LDPCs of Services, we are likely to need/want the Services to have URIs. To allow this, they can no longer be oslc:LocalResource in the Service Provider shape. We can't see any reason why a client, when performing a GET, would need a resource to be a blank node. (Having it inline is important, but it doesn't have to be a blank node to be inline). Any clients who can deal with blank nodes should be able to deal with resources with URIs, hey can just ignore the URIs.

      The TC has already voted on this, but this ticket is here (1) to help us find the information in future if we need it, and (2) to track any changes to the spec and discussions that arise from that.

            Assignee:
            James Amsden (Inactive)
            Reporter:
            Martin Pain (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: