[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hierarchy - Part 2 - How we think our data would look in ATOM

To: Yaron Goland <yarong@xxxxxxxxxxxxx>
Subject: Re: Hierarchy - Part 2 - How we think our data would look in ATOM
From: Lisa Dusseault <lisa@xxxxxxxxxxxxxxxxx>
Date: Thu, 21 Jun 2007 11:47:58 -0700
Cc: "atom-protocol@xxxxxxx" <atom-protocol@xxxxxxx>
In-reply-to: <AE9A8CBCE1A9744D975A9FBBF822DD784DE1536BE0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://www.imc.org/atom-protocol/mail-archive/>
List-id: <atom-protocol.imc.org>
List-unsubscribe: <mailto:atom-protocol-request@imc.org?body=unsubscribe>
References: <AE9A8CBCE1A9744D975A9FBBF822DD784DE1536BE0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-atom-protocol@xxxxxxxxxxxx

On first blush, this sounds extremely like XCAP: http://www.rfc-editor.org/rfc/rfc4825.txt

Lisa

On Jun 20, 2007, at 5:20 PM, Yaron Goland wrote:

One of the most important aspects of this structure is how to create URLs from it. A caller would need to know the structure's root out of band. Let's say that root is http://somewhere.live.com/somerootfeed/. In that case the root of this data structure would be URL addressable using http://somewhere.live.com/somerootfeed/com.live.livecontacts.LiveContacts. However anyone with a copy of this structure can reference any part of it at will. For example, if we wanted to address the PostalCode element inside of Location the URL would be http://somewhere.live.com/somerootfeed/com.live.livecontacts.LiveContacts/com.live.livecontacts.Contacts/com.live.livecontacts.Contact(69257004-966e-4ee1-8552-5564f17c7cad)/com.live.livecontacts.Locations/com.live.livecontacts.Location(1)/com.live.livecontacts.PostalCode.

Follow-Ups:
- RE: Hierarchy - Part 2 - How we think our data would look in ATOM
  - From: Yaron Goland

References:
- Hierarchy - Part 2 - How we think our data would look in ATOM
  - From: Yaron Goland

Prev by Date: Re: Try to social-engineer the protocol public name?
Next by Date: Re: Hierarchy - Part 2 - How we think our data would look in ATOM
Previous by thread: Re: Hierarchy - Part 2 - How we think our data would look in ATOM
Next by thread: RE: Hierarchy - Part 2 - How we think our data would look in ATOM
Index(es):
- Date
- Thread