Re: [scim] data format

A discussion on both makes sense though they should be handled separately.  The information model and supported data models ought to be orthogonal to specification of a common set of resources and attributes.  With regards to supported representations I'd be in favor of ditching XML in all forms.

On Aug 29, 2012, at 9:44 AM, Anthony Nadalin <tonynad@microsoft.com> wrote:

> Not sure I quite understand the issue, I thought the issue would be more around the wire format and API then the attributes
> 
> -----Original Message-----
> From: scim-bounces@ietf.org [mailto:scim-bounces@ietf.org] On Behalf Of Samuel Erdtman
> Sent: Wednesday, August 29, 2012 2:41 AM
> To: Leif Johansson
> Cc: scim@ietf.org
> Subject: Re: [scim] data format
> 
> Should we also look att aligning attributes to Windows Azure Active Directory Graph, or is that a completely different discussion?
> 
> regards
> //Samuel
> 
> 
> On Wed, Aug 29, 2012 at 9:08 AM, Leif Johansson <leifj@mnt.se> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> On 08/29/2012 03:17 AM, Peter Saint-Andre wrote:
>>> On 8/28/12 6:44 PM, Trey Drake wrote:
>>>> Peter,
>>> 
>>>> Would this be in addition to or in lieu of the JSON and XML formats?
>>> 
>>> Trey, that is a good question. There's an XML representation for
>>> vCard4 (RFC 6351) and I've contributed to a document defining a JSON 
>>> representation (draft-bhat-vcarddav-json), so we could potentially 
>>> use those (which seems preferable to defining yet another one-off 
>>> data model with both JSON and XML representations).
>>> Ideally, I think we'd settle on just one mandatory-to-implement 
>>> representation of whatever data model we choose.
>> 
>> My recollection is that the wg in Vancouver expressed a pretty clear 
>> consensus that it wanted to deprecate the XML representation in favor 
>> of JSON. This will obviously need to be confirmed on the list but it 
>> probably means that if vCard is to be considered that JSON version is 
>> going to be important.
>> 
>>        Cheers Leif
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>> 
>> iEYEARECAAYFAlA9v/YACgkQ8Jx8FtbMZnfcTACfRDTzx7cS742H3wIrPeAXYzD0
>> Gv8An2AIGV4JsB+gBRZgKxkIU6ZTrMLj
>> =Niog
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
> 
> 
> 
> 
> 
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim