Design Group Meeting, 19 Apr 2004
Attending: MitchKapor, LisaDusseault, AndiVajda, MimiYin, BrianDouglasSkinner
Goals
- Agree on a standard set of terminology having to do with repositories, sharing, and replication. Make sure we're all on the same page about what we think those terms mean.
Pages we walked through
Glossary terms that were created or changed as a result of the meeting
- User Repository - A User Repository is a Chandler database, where Chandler stores persistent data on the hard disk. We are not using a conventional relational database. Inspired by RDF and associative databases, OSAF put a lot of work into creating a different Data Model?. The term User Repository refers to the entire store of a single user's data managed by a single Chandler software process. In contrast, the terms User Repository Replica and Replica Set describe the different repository concepts that come up in the case of Replication.
|
- Share
- as a verb - See Trash.SharingGlossary?
- as a noun - A Share is a created when one person uses the True Trash.SharingGlossary? feature to share some content with another user. You can share an individual ContentItem, an Item Collection, or a View. If one person shares a Collection with a second person, that creates a Share. Chandler keeps track of different information about the Share, including what content is being shared, who that content is being shared with, what access permissions have been given out, and when the content was last syncronized. If the original person then shares the same content with a third person, that creates a brand new Share, and Chandler keeps track of that information separately from this information in the first Share.
|
Warning: Can't find topic Trash.SharingAddress
- Principal - A Principal is an item in the repository that represents a person (or Group) who you Share content with. In the cognitive model of the person using Chandler, a Contact and a Principal will usually be identical. In the Content Model, we will have a Kind called Principal. Principal Items will have attributes that keep track of some sort of identity or authorization information (maybe in the form of some sort of certificate or encryption key). A Principal Item might also have an attribute that points to all the access permissions that I've granted to this Principal. Each Contact in my address book will have at most one associated Principal Item.
|
- user? - The term user has recently been replaced by the term Principal?. Principal? is a specific Chandler term, with a clear technical meaning. In contrast, the word "user" is now just a fuzzy English language work, with no specific technical meaning in Chandler. A "user" is just a person who uses computer, and uses Chandler.
|
- User Repository Data - this term, and the concept it stood for, have both been deprecated, as of the Repository Terminology meeting on 19 Apr 2004
-
User Repository Data is a term that refers to just the portion of a Repository that contains a single user's items. In contrast, the term UserRepository refers to the entire data store managed by a Chandler instance.
- See Glossary: Repository
|
Warning: Can't find topic Trash.SharingCircle
- List of People You Share With-- - A list of people or Groups that the repository owner (sharer) can potentially share with. (Or, strictly speaking, not people, but Contacts -- or more strictly still, Persona+.) For a sharee to be included in someone else's List of People You Share With, they must be a Chandler user. The sharer first extends an invitation to the sharee. If the sharee accepts, an automated response is returned back to the sharer, including the sharee's X.509 certificate which is now stored as part of the user's Contact info. Once the sharee is on the sharer's SharingGlossary? Circle, the sharer can then add the sharee to AccessControlList(s) of the sharer's collections and ContentItem(s).
|
- BrianDouglasSkinner - 21 Apr 2004