[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [humanmarkup] Notes on Corrections
--
Working Draft 01, 31 October 2002
Copyright © 2002 The Organization for the Advancement of Structured Information Standards [OASIS] Table of Contents
AppendixesA. OASIS HumanMarkup Technical Committee B. Notices C. References
The Human Markup Language provides a vocabulary which will allow a wide variety of human-centric
applications to be built. It will also allow for a greater depth of information about individuals
to be assembled and used with existing applications at the discretion of the individual concerned.
This effort is motivated to fill the need to:
The Human Markup Language Primary Base Schema is not meant to be application-specific, but
rather to build a foundation on which subsequent schemata can be written to supply application-specific
vocabularies.
The scope of the Human Markup Language Primary Base Schema is very broad since it is the
foundation for applications as diverse as enabling realtime animated behaviors for 3D
representations of humans to enhancing diplomatic communication with translation services and/or
applications capable of making provisions for cultural practices.
The following terminology is used specifically for and throughout this document, without any claims of
applicability outside it. When capitalized the key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this document are to be interpreted as described in [RFC 2119].
Human Markup Language (compound term with separated words with Upper and Lower case
characters as shown) = the XML-based, special-purpose computer networking language specification
itself and all of its associated modules and sub-specifications.
The Human Markup Language Primary Base XML Schema Requirements state that this specification MUST
contain the Elements and Attributes to describe a basic or fundamental set of characteristics of
HUMAN entities and HUMAN activities as they occur in digital information systems. In keeping with
the charter of the OASIS HumanMarkup Technical Committee, which states that the aim of HumanML is
to "enhance the fidelity of human communication," this schema SHOULD specifically address the
HUMAN activity of communication.
It is not expected that the components contained in this initial version, or in any subsequent
version of the Primary Base Schema comprise a final and completely definitive resource. This is the
first and most fundamental vocabulary, and it is intended to change and evolve as our needs and
understanding evolve.
It is important to understand what the Human Markup Language is designed to be able to do, as
well as what many of us hope it will actually accomplish. There is a significant difference in
the requirements for the design of the language and the personal goals of many of the participants
in this effort.
It is apt in this case to use a trope, a figure of speech which a later schema of the Human
Markup Language will elucidate, to describe this state. This is also an aphorism.
We entered into this effort realizing that our reach will exceed our grasp.
We would like this language to improve diplomatic communications to secure World Peace, but we do
not expect such a state of affairs. That does not mean that having such a goal is unrealistic,
because without such goals, any improvement is all but impossible.
However, if we can make a contribution to improving the fidelity of human communication, we will
have accomplished much. In truth, if all we are able to do is to help ensure the accuracy and
privacy of personal information we will have accomplished much.
The table that follows summarizes the elements, attributes and types included.in this XML Schema
Specification.
The namespace for this schema is urn:oasis:names:tc:huml:xsdschema:huml-primary-base:1.0
The schema location is http://www.oasis-open.org/committees/humanmarkup/schema/
huml-primary-base-1.0.xsd
Future specifications are planned to share this namespace as part of the OASIS family of standards.
As you will note the definitions offered here begin with the the definition used in the
documentation portion of the schema. The definitions are given greater detail where it seems
appropriate. While there is an inherent organizational structure that emerges from the vocabulary
of HumanMarkup, it is not arranged into hierarchical categories. This is intentional at this
stage, since we need to ensure that any structure which is eventually adopted is only adopted
because the material itself exhibits the structure. So, to follow this approach to its logical
conclusion here, no practice has been made to group components according to any organization
other than element, complexTypes, simpleTypes and attribute/attributeGroups. Components are
introduced in alphabetical order within those basic categories.
Huml
huml is the prefix that will be associated with the Human Markup Language Specifications. It
indicates the first Human Markup Language schema and which forms the basis for succeeding
schemata.
Address Type
Address is a part of the specification which deals with Individual Human Identity and, as such, is the first of the elements which require harmonizing with existing standards. For this purpose we have imported the namespaces mentioned, and we will also ensure harmonization with the standards of the eXtensible Name Service protocol, made available by The XNS Public Trust Organization (XNSORG). This specification avoids duplicating those standards, and for this purpose defines a sequence of elements which define types of specific interest to this specification.
Human Artifact Usually acts as sign or symbol as in semiosis. Typically clothing, jewelry, pictures, trinkets, etc.,artifacts are often used to communicate information about oneself, which express one's interests, hobbies, status, or lifestyle. Artifact, as with many terms which we define for HumanMarkup purposes, also has wide use in scientific and academic contexts. We have included these domains within our scope. Therefore, there are specific usages in archeology and anthropology, which our definitions MUST support. These will be supplied in due course.
Human Belief It should also be noted that no attempt is made or envisioned to determine the veracity of any belief. We are not setting out to judge the truth of beliefs or belief systems.
Body Location
Human Communication Channel
However, it is important to provide the operational means by which sample implementations can be constructed in order to display the intended functionality of this specification, so the inclusion of this sequence of elements allows for that.
We mention this to explain why this complexType and some others include examples and elaborations while others do not. As we move into subsequent specifications it will become more apparent how these specifications and their specific schemata work together to form a modular, coherent whole.
Human Time Factors
Chronemic is the first of several complexTypes which add the most particular kind of added value which the Human Markup Language aims to provide. By this we mean the largely non-verbal range of factors which can provide greater depth of context to communications and which, by their lack in common usage, represent a set of messages that are not received clearly, if recognized, and are presently poorly understood at best.
Community - 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 communicating, 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 schemata.
Human Culture
Cultural characteristics emerge as the defining set of elements which a community shares and which distinguish the community as a cultural group per se. This partakes of the semiotic basis for communication processes as a contextual element.
To the extent possible descriptions of cultures should be compatible with academic practices and should also be generated by members of the culture being described. The huml term is Culture.
Human Emotion
With this set we will be able to produce a simple implementation to provide a clear example of the uses to which the Human Markup Language can be put. The huml term is Emotion.
Geographic Location
Haptic: Human Touching Behaviors
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 (e.g., strength of a handshake) as they affect emotional states:
1, functional/professional
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, eg, 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.
Different 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.
Human
Some explanation of the huml term Human is called for at this point. We are not adopting a particular scientific classification for the human species in this specification. We are striving to be interoperable with the community of interest which requires identity authentication, certification and verifiability, but not in the sense of taking part in those operations. Our interest is aside from establishing basic identity for we are committed to simultaneously documenting greater depth of individual information while introducing no procedures to distinguish between a living human being and a representation of a human, even if, and especially if, that representation is an agent such as a software program acting according to its instructions, whether on behalf of a living human being or not. An entity which represents itself as human, is human as far as this specification is concerned. NOTE: Starting here, we get into the types that may be moved out into application modules.
Fundamental Unit of Human Groups
This fundamental distinction is necessary in the same way that our definition of Human is necessary. By adopting no crieterion for what constitutes a Human other than self-assertion and no criterion for what constitutes a HumanGroup other than co-extistence in any kind of environment, we allow for better clarity in chronicling the set of characteristics which describe a particular Human or HumanGroup, and we require better fundamental descriptions that take nothing for granted.
Human Name Attributes This specification does not supercede the standards which have been cited, nor does it wish to establish its own different standards.It only adds its own elements which can be used in applications that do not need or for any reason do not want to use the somewhat duplicated, but interoperable, terms listed in this complexType.
Human Intent 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 a flood of elements in this complexType stemming from almost all areas of human characteristics and communications.
Kinesic: Human Movements A kinesic vocabulary is deferred to either the Secondary Base Schema or other subsequent huml schemata. The provided for this expansion is huml Kinesic.
Measurement Unit
Specifically, the complexType MeasurementUnit 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.
Human Personality Type
Proxemic: Human Space/Time Relationships
fixed feature space (unmovable boundaries, such as divisions within an office building) semi-fixed feature space such as furniture informal space includingpersonal 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.
Semiotic Communication Mode
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.
Cognitive Agent
NOTE: This element is the actor in the semiotic model of communication It is comprised of some set of processors capable of emitting, receiving and responding to signals.
Human Sign
Human Signal
Human Symbol
Human Thought NOTE: We are including this 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.
This specification contains two simpleTypes. Location A simple set of relative positional locations on an object can be referred to with the huml term locator.
range The attribute range is used for establishing the strength or intensity values of elements such as emotions.
This set of attributeGroups is used by many of our complexTypes.
age
gender
NOTE: Needs code list for values, eg, male, female, hemaphrodite, which is deferred to Secondary Base Schema.
Human Communication Attributes
Human Identifier Attributes
Human Temporal Attributes
Physical Descriptors
NOTE: The height and weight types should be numbers but have to allow for different measurement systems.
NOTE: The hair color, eyeColor, race or build attributes need code lists for values.
NOTE: Scars, Marks and Tattoos should be a complex type for graphic, location, body part.
NOTE: These issues are deferred to the Human Physical Characteristics Description Markup Language.
The following individuals helped in the formulation of this document:
TC Members Ranjeeth K. Thunga, Chair rkthunga@humanmarkup.org Joseph W. Norris, Co-Editor jwnorris@humanmarkup.org Rex Brooks, Vice Chair, Secretary, Webmaster, rbrooks@humanmarkup.org Rob Nixon, robnixon@execpc.com Sandy Ressler sressler@nist.gov Manos Batsis mbatsis@netsmart.gr James Landrum James.Landrum@ndsu.nodak.edu Invited Experts Kurt Cagle, Claude (Len) Bullard Dr. Sylvia Candelaria deRam Ph.D. Appendix B. NoticesCopyright © The Organization for the Advancement of Structured Information Standards [OASIS] 2001, 2002. All Rights Reserved. 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. Normative[RFC 2119] IETF (Internet Engineering Task Force). RFC 2119: Key words for use in RFCs to Indicate Requirement Levels.S. Bradner. 1997. [XSLT] James Clark, editor. XSL Transformations (XSLT) Version 1.0. World Wide Web Consortium, 1999. [XSL] Sharon Adler, Anders Berglund, Jeff Caruso, et. al., editors. Extensible Stylesheet Language (XSL) Version 1.0.World Wide Web Consortium, 2001. Non-Normative[PDF] Adobe Systems, Incorporated, editor. PDF Reference, Third Edition, Version 1.4. Addison Wesley. 0-201-75839-3. 2001. |
Working Draft 01, 31 October 2002
Copyright © 2002 The Organization for the Advancement of Structured Information Standards [OASIS] Table of Contents
AppendixesA. OASIS HumanMarkup Technical Committee B. Notices C. References
The Human Markup Language provides a vocabulary which will allow a wide variety of human-centric
applications to be built. It will also allow for a greater depth of information about individuals
to be assembled and used with existing applications at the discretion of the individual concerned.
This effort is motivated to fill the need to:
The Human Markup Language Primary Base Schema is not meant to be application-specific, but
rather to build a foundation on which subsequent schemata can be written to supply application-specific
vocabularies.
The scope of the Human Markup Language Primary Base Schema is very broad since it is the
foundation for applications as diverse as enabling realtime animated behaviors for 3D
representations of humans to enhancing diplomatic communication with translation services and/or
applications capable of making provisions for cultural practices.
The following terminology is used specifically for and throughout this document, without any claims of
applicability outside it. When capitalized the key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this document are to be interpreted as described in [RFC 2119].
Human Markup Language (compound term with separated words with Upper and Lower case
characters as shown) = the XML-based, special-purpose computer networking language specification
itself and all of its associated modules and sub-specifications.
The Human Markup Language Primary Base XML Schema Requirements state that this specification MUST
contain the Elements and Attributes to describe a basic or fundamental set of characteristics of
HUMAN entities and HUMAN activities as they occur in digital information systems. In keeping with
the charter of the OASIS HumanMarkup Technical Committee, which states that the aim of HumanML is
to "enhance the fidelity of human communication," this schema SHOULD specifically address the
HUMAN activity of communication.
It is not expected that the components contained in this initial version, or in any subsequent
version of the Primary Base Schema comprise a final and completely definitive resource. This is the
first and most fundamental vocabulary, and it is intended to change and evolve as our needs and
understanding evolve.
It is important to understand what the Human Markup Language is designed to be able to do, as
well as what many of us hope it will actually accomplish. There is a significant difference in
the requirements for the design of the language and the personal goals of many of the participants
in this effort.
It is apt in this case to use a trope, a figure of speech which a later schema of the Human
Markup Language will elucidate, to describe this state. This is also an aphorism.
We entered into this effort realizing that our reach will exceed our grasp.
We would like this language to improve diplomatic communications to secure World Peace, but we do
not expect such a state of affairs. That does not mean that having such a goal is unrealistic,
because without such goals, any improvement is all but impossible.
However, if we can make a contribution to improving the fidelity of human communication, we will
have accomplished much. In truth, if all we are able to do is to help ensure the accuracy and
privacy of personal information we will have accomplished much.
The table that follows summarizes the elements, attributes and types included.in this XML Schema
Specification.
The namespace for this schema is urn:oasis:names:tc:huml:xsdschema:huml-primary-base:1.0
The schema location is http://www.oasis-open.org/committees/humanmarkup/schema/
huml-primary-base-1.0.xsd
Future specifications are planned to share this namespace as part of the OASIS family of standards.
As you will note the definitions offered here begin with the the definition used in the
documentation portion of the schema. The definitions are given greater detail where it seems
appropriate. While there is an inherent organizational structure that emerges from the vocabulary
of HumanMarkup, it is not arranged into hierarchical categories. This is intentional at this
stage, since we need to ensure that any structure which is eventually adopted is only adopted
because the material itself exhibits the structure. So, to follow this approach to its logical
conclusion here, no practice has been made to group components according to any organization
other than element, complexTypes, simpleTypes and attribute/attributeGroups. Components are
introduced in alphabetical order within those basic categories.
Huml
huml is the prefix that will be associated with the Human Markup Language Specifications. It
indicates the first Human Markup Language schema and which forms the basis for succeeding
schemata.
Address Type
Address is a part of the specification which deals with Individual Human Identity and, as such, is the first of the elements which require harmonizing with existing standards. For this purpose we have imported the namespaces mentioned, and we will also ensure harmonization with the standards of the eXtensible Name Service protocol, made available by The XNS Public Trust Organization (XNSORG). This specification avoids duplicating those standards, and for this purpose defines a sequence of elements which define types of specific interest to this specification.
Human Artifact Usually acts as sign or symbol as in semiosis. Typically clothing, jewelry, pictures, trinkets, etc.,artifacts are often used to communicate information about oneself, which express one's interests, hobbies, status, or lifestyle. Artifact, as with many terms which we define for HumanMarkup purposes, also has wide use in scientific and academic contexts. We have included these domains within our scope. Therefore, there are specific usages in archeology and anthropology, which our definitions MUST support. These will be supplied in due course.
Human Belief It should also be noted that no attempt is made or envisioned to determine the veracity of any belief. We are not setting out to judge the truth of beliefs or belief systems.
Body Location
Human Communication Channel
However, it is important to provide the operational means by which sample implementations can be constructed in order to display the intended functionality of this specification, so the inclusion of this sequence of elements allows for that.
We mention this to explain why this complexType and some others include examples and elaborations while others do not. As we move into subsequent specifications it will become more apparent how these specifications and their specific schemata work together to form a modular, coherent whole.
Human Time Factors
Chronemic is the first of several complexTypes which add the most particular kind of added value which the Human Markup Language aims to provide. By this we mean the largely non-verbal range of factors which can provide greater depth of context to communications and which, by their lack in common usage, represent a set of messages that are not received clearly, if recognized, and are presently poorly understood at best.
Community - 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 communicating, 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 schemata.
Human Culture
Cultural characteristics emerge as the defining set of elements which a community shares and which distinguish the community as a cultural group per se. This partakes of the semiotic basis for communication processes as a contextual element.
To the extent possible descriptions of cultures should be compatible with academic practices and should also be generated by members of the culture being described. The huml term is Culture.
Human Emotion
With this set we will be able to produce a simple implementation to provide a clear example of the uses to which the Human Markup Language can be put. The huml term is Emotion.
Geographic Location
Haptic: Human Touching Behaviors
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 (e.g., strength of a handshake) as they affect emotional states:
1, functional/professional
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, eg, 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.
Different 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.
Human
Some explanation of the huml term Human is called for at this point. We are not adopting a particular scientific classification for the human species in this specification. We are striving to be interoperable with the community of interest which requires identity authentication, certification and verifiability, but not in the sense of taking part in those operations. Our interest is aside from establishing basic identity for we are committed to simultaneously documenting greater depth of individual information while introducing no procedures to distinguish between a living human being and a representation of a human, even if, and especially if, that representation is an agent such as a software program acting according to its instructions, whether on behalf of a living human being or not. An entity which represents itself as human, is human as far as this specification is concerned. NOTE: Starting here, we get into the types that may be moved out into application modules.
Fundamental Unit of Human Groups
This fundamental distinction is necessary in the same way that our definition of Human is necessary. By adopting no crieterion for what constitutes a Human other than self-assertion and no criterion for what constitutes a HumanGroup other than co-extistence in any kind of environment, we allow for better clarity in chronicling the set of characteristics which describe a particular Human or HumanGroup, and we require better fundamental descriptions that take nothing for granted.
Human Name Attributes This specification does not supercede the standards which have been cited, nor does it wish to establish its own different standards.It only adds its own elements which can be used in applications that do not need or for any reason do not want to use the somewhat duplicated, but interoperable, terms listed in this complexType.
Human Intent 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 a flood of elements in this complexType stemming from almost all areas of human characteristics and communications.
Kinesic: Human Movements A kinesic vocabulary is deferred to either the Secondary Base Schema or other subsequent huml schemata. The provided for this expansion is huml Kinesic.
Measurement Unit
Specifically, the complexType MeasurementUnit 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.
Human Personality Type
Proxemic: Human Space/Time Relationships
fixed feature space (unmovable boundaries, such as divisions within an office building) semi-fixed feature space such as furniture informal space includingpersonal 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.
Semiotic Communication Mode
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.
Cognitive Agent
NOTE: This element is the actor in the semiotic model of communication It is comprised of some set of processors capable of emitting, receiving and responding to signals.
Human Sign
Human Signal
Human Symbol
Human Thought NOTE: We are including this 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.
This specification contains two simpleTypes. Location A simple set of relative positional locations on an object can be referred to with the huml term locator.
range The attribute range is used for establishing the strength or intensity values of elements such as emotions.
This set of attributeGroups is used by many of our complexTypes.
age
gender
NOTE: Needs code list for values, eg, male, female, hemaphrodite, which is deferred to Secondary Base Schema.
Human Communication Attributes
Human Identifier Attributes
Human Temporal Attributes
Physical Descriptors
NOTE: The height and weight types should be numbers but have to allow for different measurement systems.
NOTE: The hair color, eyeColor, race or build attributes need code lists for values.
NOTE: Scars, Marks and Tattoos should be a complex type for graphic, location, body part.
NOTE: These issues are deferred to the Human Physical Characteristics Description Markup Language.
The following individuals helped in the formulation of this document:
TC Members Ranjeeth K. Thunga, Chair rkthunga@humanmarkup.org Joseph W. Norris, Co-Editor jwnorris@humanmarkup.org Rex Brooks, Vice Chair, Secretary, Webmaster, rbrooks@humanmarkup.org Rob Nixon, robnixon@execpc.com Sandy Ressler sressler@nist.gov Manos Batsis mbatsis@netsmart.gr James Landrum James.Landrum@ndsu.nodak.edu Invited Experts Kurt Cagle, Claude (Len) Bullard Dr. Sylvia Candelaria deRam Ph.D. Appendix B. NoticesCopyright © The Organization for the Advancement of Structured Information Standards [OASIS] 2001, 2002. All Rights Reserved. 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. Normative[RFC 2119] IETF (Internet Engineering Task Force). RFC 2119: Key words for use in RFCs to Indicate Requirement Levels.S. Bradner. 1997. [XSLT] James Clark, editor. XSL Transformations (XSLT) Version 1.0. World Wide Web Consortium, 1999. [XSL] Sharon Adler, Anders Berglund, Jeff Caruso, et. al., editors. Extensible Stylesheet Language (XSL) Version 1.0.World Wide Web Consortium, 2001. Non-Normative[PDF] Adobe Systems, Incorporated, editor. PDF Reference, Third Edition, Version 1.4. Addison Wesley. 0-201-75839-3. 2001. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC