OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [camp] Mutability metadata


I think it is on the instance of the collection. It tells you that if you were to POST to this particular collection you would have to set these values.

But I could be wrong.

Mike

Dr. Mike Norman | Vice President | Cloud Development | JPMorgan Chase  
45 Waterloo Street, Glasgow, G2 6HS | Phone: +44 (0)141 2280 0853 | michael.norman@jpmchase.com

-----Original Message-----
From: camp@lists.oasis-open.org [mailto:camp@lists.oasis-open.org] On Behalf Of Anish Karmarkar
Sent: 26 February 2016 00:06
To: camp@lists.oasis-open.org
Subject: [camp] Mutability metadata

On the call today Mike raised the issue of providing metadata for attributes that can be set on creation but cannot be changed later.

Thinking more on this (and I think Gil may have already pointed this
out): that kind of mutability metadata made sense when we specified it on the 'type'. Now that we have it on the instance, I don't think you can use the current instance-specific 'metadata' attribute to specify this. You'll have to stick this somewhere else (type or collection or the method description).

Did I misunderstand it?

--Anish

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


This communication is for informational purposes only.  It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.  All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice.  Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC").

This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED.  If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.  Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use.  Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations.

Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]