closed 4.2.1.1 2005-02-02T15:07:44.342-06:00 2004-06-12T21:35:54.503-06:00 TSD4.2 Archaeological Markup Language (ArchaeoML), version 0.9, February 2006. Created by David Schloen of the University of Chicago. Person document type. A Person document represents a person or organization, including historical and fictional persons and organizations. A person may be a registered user of the OCHRE system. In that case, additional userInfo is needed. Here the categories are for the individual User's MY collection. Note: category names generally correspond to one of the other doctypes. In the cases where they do not have a corresponding doctype, they refer to collections (trees, relationships, etc.) of another doctype (e.g. Maps category is a collection of trees, etc. of some custom tree-type, in this example -map-). [We may not, in fact, allow Users to have instances of ALL of these categories in their own MY collection.] Any number of projects can be associated with the user, making available to that user the sets of variables, values, predefinitions, equivalences, and dependencies belonging to those projects. Every user associated with a project is assigned access rights, at the category-level, to that project by that project's administrator. In this case, will always be of type -project-. Here the categories are for the individual User's MY collection. Note: category names generally correspond to one of the other doctypes. In the cases where they do not have a corresponding doctype, they refer to collections (trees, relationships, etc.) of another doctype (e.g. Maps category is a collection of trees, etc. of some custom tree-type, in this example -map-). [We may not, in fact, allow Users to have instances of ALL of these categories in their own MY collection.] A user can save any number of query-result sets, each represented by a Set document. The docID here must refer to a Set document. nestedVariableIndex nestedValueIndex nestedDocIdIndex nestedLinkIndex