[Dev] Data Model Issues Meeting

[Katie Capps Parlante]

Hi Ted and Andi,

I have a writeup of data model open issues, from the apps team's recent 
experience: 
http://wiki.osafoundation.org/twiki/bin/view/Chandler/ApplicationDataModelOpenIssues

I didn't structure it into Ted's two categories, although I think that's 
a great way of looking at it. I was more focused on just collecting our 
recent experience, and writing down the history of how/why some 
decisions were made. You can take that input and structure the issues as 
you like for the meeting. I've also included a lot of parcel issues, 
because it was at times hard to discuss one without the other.

We can leave some of these issues for seperate meetings, including the 
threading issue.

Discussion of these issues might be best in email on the dev list (apart 
from the meeting). Folks can add issues or comments to the wiki page, 
but I'm not expecting it to continue to be "live" much after the meeting 
tomorrow.

Cheers,
Katie

Ted Leung wrote:

> Hi folks,
> 
> One of the things that we need to do for the 0.4 release is take stock 
> of where we are with the Data Model implemented by the Chandler 
> repository, and make any changes that are needed.  To get things going, 
> I'd like to have a meeting on Thursday, March 11th to get started.  3pm 
> has been suggested as a good time. (As an experiment in calendaring, 
> I've made my iCal work calendar available here: 
> http://www.sauria.com/~twl/calendars/Work.ics)
> 
> The OSAF staff that need to be in the meeting are (this is also an 
> experiment in being more public about meetings):
> Ted Leung (moderator)
> Andi Vajda
> John Anderson
> Morgen Sagen
> Katie Parlante
> 
> If I've left off anyone who should be included please let me know.  
> Also, could someone please arrange for a meeting room for people on site?
> 
> I think that there are two categories of issues:
> 
> 1. Issues with the Abstract/Conceptual data model.  An example would be 
> "are we actually using Alias types"
> 2. Issues with the implementation of the data model.  An example would 
> be "the API for Lob derived types" is unwieldy.
> 
> To get things started off, here is my list of issues:
> 
> Type 1:
> 1. Aliases - usage cases
> 2. Structs - usage cases
> 3. List vs dict ref collections - resolve the status
> 
> Type 2:
> 1. How are line endings stored in strings used in the repository?  Is 
> this an issue for portable (cross platform) repository files? (Is this a 
> goal?)
> 2. I would like to see us make the LOB API easier to use, especially for 
> Text.
> 3. List ref collections are not indexable (no random access that isn't 
> O(n))
> 
> Please reply with a note containing your issues.  I'll try to collate 
> everything before the meeting, and either mail it out or put it on the 
> wiki.   The meeting notes will go up on the wiki afterwards.
> 
> ----
> Ted Leung                 Open Source Applications Foundation (OSAF)
> PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42
> 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> 
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev