<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 U (http://www.xmlspy.com) by Rex Brooks (Humanmarkup.org, Inc) -->
<xs:schema targetNamespace="http://www.oasis-open.org/committees/humanmarkup/schema/huml-primary-base-1.0.xsd" xmlns:n="urn:oasis:names:tc:ciq:xsdschema:xNL:2.0" xmlns:a="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.oasis-open.org/committees/humanmarkup/schema/huml-primary-base-1.0.xsd" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<!--<xs:import namespace="http://ns.hr-xml.org/CPO/PersonName-1_2/PersonName-1_2.xsd"/>
	<xs:import namespace="http://ns.hr-xml.org/CPO/PostalAddress-1_2/PostalAddress-1_2.xsd"/> 
	<xs:import namespace="http://www.fdge.gov/metadata/fdgc-std-001-1998.dtd"/>
	<xs:import namespace="http://www.placeholder.org/placeholder.xsd"/>
	<xs:import namespace="urn:oasis:names:tc:ciq:xsdschema:xNL:2.0" schemaLocation="xNL.xsd"/>
	<xs:import namespace="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0" schemaLocation="xAL.xsd"/>-->
	<xs:element name="Huml">
		<xs:annotation>
			<xs:documentation>huml is the prefix that will be associated with the Human Markup Language Specifications. It indicates the first Human Markup Language schema, and it forms the basis for succeeding schemata.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:annotation>
		<xs:documentation xml:lang="en">
			Human Markup Language Schema, Version 1.0
			Copyright 2002 The Organization for the Advancement of Structured Information Standards. All rights reserved.  
			This schema is the primary base schema from which subsequent schemata and specific HumanML applications are derived.  Note this is the first working draft.
			OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.
			OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
			This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
			This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
			OASIS has been notified of intellectual property rights claimed in regard to some or all of the contents of this specification. For more information consult the online list of claimed rights.
		</xs:documentation>
		<xs:appinfo>NONE</xs:appinfo>
	</xs:annotation>
	<!-- Global Section -->
	<!-- Begin Simple Types -->
	<xs:simpleType name="range">
		<xs:restriction base="xs:decimal">
			<xs:minInclusive value="0"/>
			<xs:maxInclusive value="1"/>
		</xs:restriction>
	</xs:simpleType>
	<!-- End Simple Types -->
	<!-- Begin Attribute Groups -->
	<xs:attributeGroup name="humlIdentifierAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Identifier Attributes
				This huml term humlIdentifierAtts is used for identifier uniqueness and huml element names. It is used to indicate use in indentifying characteristics.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="id" type="xs:ID" use="required"/>
		<xs:attribute name="humlName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="humlTemporalAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Temporal Attributes
				This huml term humlTemporalAtts is used for identifier uniqueness and huml element names. It is used to indicate specified periods of time from one date and/or time to a later date and/or time.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="id" type="xs:ID" use="required"/>
		<xs:attribute name="humlName" type="xs:string" use="required"/>
		<xs:attribute name="fromDate" type="xs:dateTime" use="required"/>
		<xs:attribute name="toDate" type="xs:dateTime" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="humlCommAtts">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Communication Attributes
				This huml term humlCommAtts is used for identifier uniqueness and huml element names. It is used to indicate use in communication.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="id" type="xs:ID" use="required"/>
		<xs:attribute name="humlName" type="xs:string" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="age">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Age
				The huml attributeGroup age is a set of attributes for documenting or determining the age of a human.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="dateOfBirth" type="xs:date" use="required"/>
		<xs:attribute name="dateOfDeath" type="xs:date" use="required"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="physicalDescriptors">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Physical Descriptors
				The huml term phsycialDescriptors is a set of attributes for a physical description of a human.  
				NOTE: The height and weight types should be numbers but have to allow for different measurement systems.
				NOTE: The hair color, eyeColor, build attributes need code lists for values.
				NOTE: Scars, Marks and Tattoos should be a complex type for graphic, location, body part
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="height" type="xs:string"/>
		<xs:attribute name="weight" type="xs:string"/>
		<xs:attribute name="hairColor" type="xs:string"/>
		<xs:attribute name="eyeColor" type="xs:string"/>
		<xs:attribute name="build" type="xs:string"/>
		<xs:attribute name="scarsMarksTattoos" type="xs:string"/>
	</xs:attributeGroup>
	<xs:attributeGroup name="gender">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Gender
				This term gender is a set of attributes for documenting the gender of a human.  
				NOTE: Needs code list for values, eg, male, female, hemaphrodite   
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute name="genderAtBirth" type="xs:string"/>
		<xs:attribute name="currentGender" type="xs:string"/>
		<xs:attribute name="impersonator" type="xs:boolean"/>
	</xs:attributeGroup>
	<!-- End Attribute Groups -->
	<!-- Begin Global Attributes -->
	<xs:attribute name="intensity">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Intensity
				This is a positive number between 0 and 1 used to set a relative scale 
            of the intensity or strength of some behavior, such as a handshake or an emotion.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
	</xs:attribute>
	<!-- End Global Attributes -->
	<!-- Begin Complex Types -->
	<!-- Begin Physical Dimensions -->
	<xs:complexType name="MeasurementUnit">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Measurement Unit
				Used to create measurement values.  
				This complexType is used to establish the use of a recognized measurement system.    Systems of measurement vary by unit, name (for example English units vs metric units) and measurement type.  For example, for radius used to determine proximity some unit of distance is needed. We anticipate a corresponding RDF Schema to act as a facility for connecting a resource reference to an application that wishes to use this and the subsequent huml schema. We may decide to include elements from such reference schemata or to import the namespaces of such measurement system standards.
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
	</xs:complexType>
	<xs:simpleType name="Locator">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Location
				A simple set of names of relative positional locations on an object can be referred to with the huml term Locator.    
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="upper"/>
			<xs:enumeration value="lower"/>
			<xs:enumeration value="back"/>
			<xs:enumeration value="front"/>
			<xs:enumeration value="inner"/>
			<xs:enumeration value="outer"/>
			<xs:enumeration value="left"/>
			<xs:enumeration value="right"/>
			<xs:enumeration value="top"/>
			<xs:enumeration value="bottom"/>
		</xs:restriction>
	</xs:simpleType>
	<!-- End Physical Dimensions -->
	<!-- Begin Human Physical Characteristics -->
	<xs:attribute name="bodyPart">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Body Part
				This is a simple body part.  Used in haptics, artifacts, kinesics, etc.  
				  <xhtml:strong>NOTE: </xhtml:strong>This element will be enumerated in a subsequent huml schema. The values included here serve as examples, as placeholders which will likely be replaced by importing the namespace and schema location of the subsequent schema.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:simpleType>
			<xs:restriction base="xs:string">
				<xs:enumeration value="arm"/>
				<xs:enumeration value="leg"/>
				<xs:enumeration value="head"/>
			</xs:restriction>
		</xs:simpleType>
	</xs:attribute>
	<xs:complexType name="BodyLocation">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Body Location
				The huml term BodyLocation is used for a location on a body part.  Used in haptics, artifacts, etc.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute ref="bodyPart"/>
		<xs:attribute name="location" type="Locator"/>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<!-- End Human Physical Characteristics -->
	<!-- Begin Communication Modes and Constraints -->
	<xs:complexType name="Kinesic" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Kinesic: Human Movements
				Communicational Kinesics constitute some vocabulary of body language used to portray moods and emotions and to add emphasis to verbal communication. As a study concerned with how bodily and facial gestures function as a factor in communication, kinesics is fairly well understood. For our purposes we expect enumeration of body language gestures to be included in culture-specific subsets.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlCommAtts"/>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attribute ref="intensity"/>
	</xs:complexType>
	<xs:complexType name="Proxemic" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Proxemic:  Human Space/Time Relationships
				Proxemic factors in communication indicate both time and space as well as relative body positions (given some organization of the features of the space in which communication occurs). The huml term Proxemic includes physical distance or closeness maintained between individuals, which affect messageTypes such as body heat they give off, odors perceived in social situations, angles of vision they maintain while talking and the like. Derived from proximity, proxemic considerations include:  
				fixed feature space (unmovable boundaries, such as divisions within an office building),,
				semi-fixed feature space such as furniture
				informal space including
					personal distance
					social distance 				
				NOTE: Proxemic elements will fall into two main categories, communication and spatial. Because there is not a significant body of literature supporting these categorizations, it is deferred to the Secondary Base Schema and subsequent huml schema to enumerate and extend.   
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlCommAtts"/>
		<xs:attributeGroup ref="humlTemporalAtts"/>
	</xs:complexType>
	<xs:complexType name="Haptic" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Haptic:  Human Touching Behaviors
				Haptics refers to the study of touching behavior in different societies and cultures. Haptic is a communication factor that applies to a wide variety of behaviors indicating state of mind and emotion. It can range widely, as from hostility (kicking) to intimacy (kissing). Haptics is also the study of tactile response in a strictly scientific framework, such as studies about feedback in touch-controlled computer pointing devices such as the mouse and keyboard. Because of its range of applications, haptic will require more consideration than a set of simpleType elements.				The HumanML haptic model is based on the strength, location, and body part used in a touching behavior.  It does not provide a semantic model for interpretation.To understand how to use this complexType, an example is provided.  Theorists have proposed, for example, five degrees of the haptic and an intensity value for force of behavior (eg, strength of a handshake) as they reflect emotional states:   
				1. functional/professional
				2. social/polite
				3. friendship/warmth
				4. love/intimacy
				5. sexual arousal
				HumanML notes such theories but does not assign values per the abstract haptic definition, instead leaving that to the derived application languages. This is because there can be differing applicable models, e.g., the strength of the act of physical therapy can and does approach that of sexual arousal, yet the model shown above might classify this as a functional/professional contact, indicating a low degree of arousal.
				Some models would claim that sexual and emotional arousal are different states. Contact strengths could be defined for individuals, cultures and communities, but the scale has to be assigned so that, for instance, on a scale of zero through one, .20 is (1), .40 is (2), .60 (3) and so on, expresses a norm.  For an individual, the rating expresses a real state of arousal based on a touch.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="touchWhere" type="BodyLocation"/>
			<xs:element name="touchWith" type="BodyLocation"/>
		</xs:sequence>
		<xs:attributeGroup ref="humlCommAtts"/>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attribute ref="intensity"/>
	</xs:complexType>
	<xs:complexType name="Chronemic" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Time Factors
				Chronemic is used for time characterization. Human awareness and use of time can be associated with cultural characteristics and as a non-verbal communication element. The study of chronemics as a variable in communications has an acceptable body of support. Chronemics can be seen to be used very differently with respect to individuals and cultures. Time perceptions include punctuality, willingness to wait, and interactions. Time use affects lifestyles, daily agendas, speed of speech and movements, how long people are willing to listen, etc. However as both cultural characteristic and communication factor, chronemic factors exhibit two states, monochronic and polychronic.  
				Monochronic: one thing at a time (sequential).
				Polychronic: several things at once  (parallel).
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attributeGroup ref="humlCommAtts"/>
		<xs:attribute name="chronemicType">
			<xs:simpleType>
				<xs:restriction base="xs:string">
					<xs:enumeration value="characteristicFactor"/>
					<xs:enumeration value="communicationFactor"/>
					<xs:enumeration value="monochronic"/>
					<xs:enumeration value="polychronic"/>
				</xs:restriction>
			</xs:simpleType>
		</xs:attribute>
	</xs:complexType>
	<xs:complexType name="Artifact" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Artifact
				A trace object, usually human made, and/or assigned human meaning. Usually acts as sign or symbol. Typically clothing, jewelry, pictures, trinkets, etc., are artifacts often used to communicate information about oneself, which express one's interests, hobbies, status, or lifestyle. There are specific usages in archeology and anthropology, which our definitions MUST support.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
		<xs:attributeGroup ref="humlCommAtts"/>
		<xs:attributeGroup ref="humlTemporalAtts"/>
	</xs:complexType>
	<!-- End Communication Modes and Constraints -->
	<!-- Begin Internal Human States -->
	<xs:complexType name="Belief" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Belief
				The huml term Belief designates any human belief. A human belief is a conviction held by a human or humanGroup of the truth of a statement or assertion.A distinction will inevitably be made between a simple belief, such as believing in deity, and a belief system such as Judaism or Buddhism, which could be the basis of extension for this complexType, but for our purpose the simplest definition will be adopted for this schema.   
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<xs:complexType name="Emotion" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Emotion
				A basic set of primitive human emotions; the six basic emotions that have well-documented facial expressions associated with them, to which we can assign strength values in the range we have established as a relative measure of intensity and which we can take as standard primitives are provided.  
				<xs:sequence>
					<xs:element name="sadness" type="boolean" default="true"/>
					<xs:element name="joy" type="boolean" default="true"/>
					<xs:element name="anger" type="boolean" default="true"/>
					<xs:element name="fear" type="boolean" default="true"/>
					<xs:element name="disgust" type="boolean" default="true"/>
					<xs:element name="surprise" type="boolean" default="true"/>
				</xs:sequence>
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute ref="intensity"/>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<xs:complexType name="Intent" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Intent
				Intent is the state of mind and emotion, characterized by purpose and volition, with which a human acts or prepares to act
				NOTE: This complexType is a key factor in communication   
				An example of Intent is the planning of a presentation.  It is almost guaranteed that there will be flood of elements in this complexType stemming from almost all areas of human characteristics and communications.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute ref="intensity"/>
		<xs:attributeGroup ref="humlCommAtts"/>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
		<xs:attributeGroup ref="humlTemporalAtts"/>
	</xs:complexType>
	<xs:complexType name="Thought" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Thought
				The physiological process of mentation.  
				 NOTE: We are including the complexType Thought without any stipulation for how a set of thought elements or types could or should or will be constructed. There are any number of ways this concept might be used, but an accepted definition, which involves the much-disputed concept of what constitutes self-consciousness or awareness in terms other than physiological, is not within our present scope to support or defend.  
				An example of Thought which could be described as a process from the viewpoint of an observer, though perhaps not characterized as coherent awareness or communication would be the brain activity of an autistic person or someone in a coma or even someone asleep.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attribute ref="intensity"/>
		<xs:attributeGroup ref="humlCommAtts"/>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
		<xs:attributeGroup ref="humlTemporalAtts"/>
	</xs:complexType>
	<!-- End Internal Human States -->
	<!-- Begin Channel Types -->
	<xs:complexType name="Channel" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Communication Channel
				A Channel is one of the senses or faculties by which a Human communication is transmitted and/or received. These elements will be enumerated in subsequent huml schemata. The elements included here serve as examples, as placeholders for sensory receiving or input channels which will likely be replaced by importing the namespace and schema location of the subsequent huml schema.  
				<xs:sequence>
					<xs:element name="sight" type="boolean" default="true"/>
					<xs:element name="hearing" type="boolean" default="true"/>
					<xs:element name="touch" type="boolean" default="true"/>
					<xs:element name="taste" type="boolean" default="true"/>
					<xs:element name="smell" type="boolean" default="true"/>
					<xs:element name="kinesthetic" type="boolean" default="true"/>
				</xs:sequence>
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attribute ref="intensity"/>
	</xs:complexType>
	<!-- End Channel Types -->
	<!-- Begin Semiosis Section -->
	<xs:complexType name="Semiosis" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Semiotic Communication Mode
				Semiosis is a meaningful exchange of signs, signals and symbols among cognitive agents.  
				 NOTE: This process is the model of the human communication process upon which HumanML is based. It can be, and we expect that it will be further enumerated by semiotic types and extended in the Secondary Base Schema and subsequent huml schemata.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attributeGroup ref="humlCommAtts"/>
	</xs:complexType>
	<xs:complexType name="Semiote" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Cognitive Agent
				A Semiote is a cognitive agent who participates in meaningful signal exchange among cognitive agents.  
				NOTE: This element is the actor in the semiotic model of communication It isset of processors capable of emitting, receiving and responding to signals.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlCommAtts"/>
	</xs:complexType>
	<xs:complexType name="Sign" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Sign
				A concrete denotation of a specific meaning.  Common signs include pictures or drawings, 
          although a human posture like a clenched fist, an outstretched arm, or a hand posed in a "Stop" 
          gesture may also serve as signs. The main difference between a sign and a signal is that a sign 
          has a specific meaning and usually requires training.  For example, an ape or dog can be taught 
          to respond consistently and appropriately to signs but teaching them Morse Code (a signal) is 
          much harder if at all doable.  
				Signs communicate simple messages swiftly efficiently, may be culturally and location-specific, 
          that is, meaningful in a locale (a stop sign) or culture (the Hindu greeting of folded hands).  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlCommAtts"/>
	</xs:complexType>
	<xs:complexType name="Signal" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Signal
				A perceptible change in an environmental factor that can be used to transfer meaning. The basic function of such signals is to provide the change of a single environmental factor to attract attention and to transfer meaning. The vocalization of language is a clear example.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attributeGroup ref="humlCommAtts"/>
	</xs:complexType>
	<xs:complexType name="Symbol" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Symbol
				Any device with which an abstraction can be made.  May include written and spoken language as well as visual objects.  May include a process of symbolization.May be culturally specific and often used as a means to communicate cultural values.May and often do appear in clusters and depend upon one another for meaning and value. 
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlCommAtts"/>
	</xs:complexType>
	<!-- End Semiosis Section -->
	<!-- Begin Individual Human and Identity Section -->
	<xs:complexType name="Human">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human
				An entity which exhibits the basic characteristics of humans.  
				 NOTE: Starting here, we get into the types that may be moved 
          out into application modules.   
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="HumanNameElements">
				<xs:attributeGroup ref="humlIdentifierAtts"/>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:complexType name="HumanNameElements">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				HumanML Name Attributes
				HumanNameElements is a set of attributes for documenting the names and aliases of real or artificial humans, communities, businesses, etc.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="last" type="xs:string"/>
			<xs:element name="first" type="xs:string" minOccurs="0"/>
			<xs:element name="middle" type="xs:string" minOccurs="0"/>
			<xs:element name="prefix" type="xs:string" minOccurs="0"/>
			<xs:element name="suffix" type="xs:string" minOccurs="0"/>
		</xs:sequence>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
		<xs:attribute name="isAlias" type="xs:boolean"/>
	</xs:complexType>
	<xs:complexType name="Address">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Address Type
				Address refers to an address in a named address system, such as street, city, state, etc.  Note that this needs to be code-based, that is, adaptable to different naming conventions of international locales.  For this purpose we have imported the Extensible Address Language from the OASIS Customer Information Quality Technical Committee under review as an OASIS standard and the PostalAddress Standard XML Schema from the Human Resources Consortium (HR-XML).
	            </xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="postal" type="xs:string"/>
			<xs:element name="residential" type="xs:string" minOccurs="0"/>
			<xs:element name="email" type="xs:string" minOccurs="0"/>
			<xs:element name="previous" type="xs:string" minOccurs="0"/>
			<xs:element name="current" type="xs:string" minOccurs="0"/>
		</xs:sequence>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<xs:complexType name="Personality" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Personality Type 
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<!--End Individual Human and Identity Section-->
	<!--Begin Human Group Section-->
	<xs:complexType name="HumanGroup">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Fundamental Unit of Human Groups
				A HumanGroup is the most basic, fundamental unit of Humans grouped or grouping together. It is defined as two or more humans gathered in an environment. It is necessary because it is possible for there to exist a HumanGroup that does not constitute a community.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<xs:complexType name="Community">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Abstract Human Organization
				A HumanGroup attains the status of Community when it exhibits organization usually typified by a set of beliefs held in common or actions performed together. These might be communication, creating some common artifact, a common purpose such as study, worship, business, sports, etc. Criteria for inclusion will be specific to named communities which will in turn be specified in subsequent huml schema.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<xs:complexType name="Culture" abstract="true">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Human Culture
				Cultural characteristics emerge as the defining set of elements which a community shares and which distinguish the community as a culture per se. This partakes of the semiotic basis for communication processes as a contextual element.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlTemporalAtts"/>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<!-- Extensions for World Descriptors and Contexts -->
	<xs:complexType name="GeoLocator">
		<xs:annotation>
			<xs:documentation xml:lang="en">
				Geographic Location
				The huml term GeoLocator is used for a 3D address type based on map coordinate systems. We will provide references to standards. These will include the Geospatial Positioning Accuracy StandardsPart 4: Standards of Architecture, Engineering, Construction (A/E/C) and Facility Management FGDC-STD-007.4-2002 adopted by the Federal Geographic Data Committee and the ISO candidate standard specification amendment to the ISO VRML97 standard (ISO/IEC 14772-1 1997) which can be referenced at http://www.geovrml.org/1.1/doc/index.html. Other International Standards may also be cited.  
			</xs:documentation>
			<xs:appinfo>NONE</xs:appinfo>
		</xs:annotation>
		<xs:attributeGroup ref="humlIdentifierAtts"/>
	</xs:complexType>
	<!-- End Extensions for World Descriptors and Contexts -->
	<!-- End Complex Types -->
	<!-- End Global Section -->
</xs:schema>

