[OASIS Issue Tracker] (OSLCCORE-50) Should we omit the "read-only" values in the discovery resource shapes?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Martin Pain created OSLCCORE-50:
-----------------------------------

             Summary: Should we omit the "read-only" values in the discovery resource shapes?
                 Key: OSLCCORE-50
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-50
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
            Reporter: Martin Pain
            Assignee: James Amsden
            Priority: Minor


This was the case in v2 (so perhaps we can defer this), but I don't see why we set "read-only" to true for these properties. I would have thought some servers might allow clients to create new ServiceProviders, or modify ones they previously created. e.g. a generic ServiceProviderCatalog server that acts as a registry of other servers. I'd suggest we have read-only as not specified (if that won't be problematic), but this is probably too big a thing to consider at this stage. It's not really causing a problem.

(Note: dcterms:identifier on oslc:Publusher - §A.6 - has an "unspecified" read-only value. Should it be consistent with the others?)



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)