[humanmarkup] Re: Latest draft of HM.AI.requirements

[Rex Brooks <rexb@starbourne.com>]

Hi Rob,

The IETF RFC 2119 document uses all caps for MUST, MUST NOT, SHOULD, 
SHOULD NOT, etc. The double quote marks were holdovers from 
Ranjeeth's previous document and Manos' original pass. Small, but 
significant detail. There is a yet a third variation from the W3C, 
from which I somehow have to pry the WSIA and which was just used as 
a trial format by yet another well-intentioned initial author. I will 
be attempting to become a member of the liaison group from OASIS to 
these other organizations, since I am also a de facto member of W3C 
and ISO through the Web 3D Consortium and I would like to see a 
synchronization of this terminology.

As you can see, I'm up death early, rather than death late this 
morning, working on what amounts to a trial run or practice STTR 
Proposal, which may possibly be used, but which will certainly be 
used in a later SBIR Proposal when the new round starts in May. In 
case I haven't informed you, there is a fairly large area in this 
proposal which needs to be filled by Humanmarkup.org, Inc. and for 
which I was hoping to enlist you, but which I won't finalize for some 
time yet to come. Finishing a first draft of that proposal is my main 
objective today.

I hope to chat with you in our near death early chat this morning at 
8 a.m. EST.

Ciao,
Rex


At 11:10 PM -0600 3/30/02, Rob Nixon wrote:
>Here is the final draft of the HM.AI.requirements document.  It reflects some
>of the updated text of the master HM.requirements document related to the AI
>secondary schema.  I've also included it as an attachment.
>
>Thanks,
>Rob
>
>----
>
>HM.AI.REQUIREMENTS
>last updated: 31March 2002
>(this document describes the different requirements for the secondary AI Human
>Markup Schema specifications of the base HumanML Schema)
>---------------------
>
>
>----------------
>ABSTRACT:
>----------------
>This document specifies goals, requirements, and usage scenarios for the for
>the Human  Markup Language secondary AI Human Markup Schema.
>
>----------------
>DOCUMENT STATUS:
>----------------
>
>The design of HumanML secondary AI Human Markup Schema is designed to address
>the broad spectrum of possible AI related applications in which HumanML would
>play a role.  This Requirements Document  is designed in the expectation that
>this document, the secondary AI Human Markup Schema, will be modified as
>needed.
>
>This document is normative as of the date it is adopted by the OASIS
>HumanMarkup Technical Committee.
>
>----------------
>TERMINOLOGY:
>----------------
>As with the base HumanML Schema, for the purposes of clarity, we offer these
>definitions for terms we use in general and which may appear in this document
>but are not specific to this document:
>
>Human Markup Language AI (a compound term with separated words with Upper and
>Lower case characters as shown) = the XML-based computer networking language
>AI specification itself and all of its associated modules and
>sub-specifications.
>
>HumanML.AI(compound term with Upper and Lower case characters as shown) = the
>Human Markup Language AI Specification.
>
>HumanMarkupAI (compound term with Upper and Lower Case characters as shown) =
>the collective effort to build the Human Markup Language AI sub-specification,
>also used for similar purposes in the name of the OASIS HumanMarkup Technical
>AI Sub-Committee.
>
>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 interpretated as described in RFC 2119. ref.:
>http://www.ietf.org/rfc/rfc2119.txt
>
>"HumanAI"
>
>When enclosed in double quote marks, as above, it is used as a name for what
>the HumanMarkup AI sub-Initiative aims to encapsulate into HumanML.AI. Used
>thus, this term transcends reference to any single biological entity's or to
>the collective biological species of Homos Sapiens simulation of cognitive
>function, and is inclusive of all self- to species-conscious effort throughout
>our history to understand ourselves and our cognitive processes.
>
>"Must"
>When enclosed in double quote marks, as above, this word, means that the
>requirement item has been classified as an absolute requirement.
>
>"Should"
>When enclosed in double quote marks, as above, this word means that it is
>believed by this Technical Committee that the requirement item will prove
>itself as absolute in the future, but has not yet been classified as such and
>may be overridden by another requirement.
>
>"May"
>When enclosed in double quote marks, as above, this word means that the
>requirement item can become a requirement in the future, but further study is
>needed.
>
>
>----------------
>CLASSIFICATION:
>----------------
>Secondary Schemata (Was: vocabularies)
>
>This document classifies the secondary AI "module" as a Secondary Schema of
>the Primary HumanML Schema on an equal footing with all other Secondary
>Schemata as being capable of engendering and containing further modules which
>can be classified as derivative or submodules as appropriate, but which may
>always be seen as existing in the Secondary grouping on an equal footing.
>
>----------------
>EXISTING STANDARDS:
>----------------
>The AI community in concert with the Internet community is attempting to
>derive useful crossover applications. This naturally leads to potential
>overlap among developing AI-Internet standards.
>
>HumanMarkupAI standards "must" always be based on the most widely accepted,
>non-proprietary standards available. At this time this is XML,
>http://www.w3.org/TR/REC-xml
>
>The Human Markup Language AI specification "should" not attempt to produce new
>standards in relation to informational subject or topic areas already
>addressed or covered by the above-referenced most widely accepted standards.
>
>HumanML.AI "should"  incorporate and/or provide for interoperabiity with the
>above-referenced most widely accepted developing standards (or pseudo
>standards), such as RuleML, DAML+OIL, and the Artificial Intelligence Markup
>Language (AIML), but allow for extensibility.
>
>HumanML.AI "should" use the most effective standards, protocols and
>methodologies available to encapsulate what is "HumanAI" in a well formed data
>wrapper.
>
>----------------
>REQUIREMENTS:
>----------------
>HumanML.AI "must" be open, which means readily available in its whole and its
>parts without recourse to restricted access by any criteria.
>
>HumanML.AI "must" be non-proprietary, which means that no private ownership
>may be asserted over its whole or its parts and it must also be unencumbered
>by any pre-existing Intellectual Property Rights for its whole or any part of
>its specifications.
>
>HumanML.AI "must" be public, which means available freely and without any
>charge added to the cost of transmission to anyone by common means such as the
>World Wide Web or International Postal Services.
>
>HumanML.AI "must" be standard, which means that it is uniform in its whole and
>its parts with regard to any and all applications which make use of it.
>
>HumanML.AI " must " be vendor and/or platform neutral.
>
>----------------
>COMPATIBILITY:
>----------------
>HumanML.AI " must " conform to XML syntax and rules.
>
>----------------
>EXTENSIBILITY:
>----------------
>HumanML.AI Schema "must" be extensible.
>
>Terseness "should" be preferred.
>
>
>----------------
>INTERNATIONALIZATION:
>----------------
>Since XML is Unicode, HumanML.AI implementations "must" support this by
>default and in a well-defined syntax. This section will most likely span a
>"syntax guidelines rule " applicable to the HumanML.AI module for a common
>syntax definition.  (This requirement will reflect how syntax inclusion is
>handled by the base HumanML specification. )
>
>
>----------------
>TRUST/DIGITAL SIGNATURES:
>----------------
>HumanML.AI, and the HumanMarkupAI "should" take into account issues of trust,
>digital signatures, and privacy.
>
>(Note: This requirement will reflect how HumanML in general handles the issues
>of trust, digital signatures, and privacy)
>
>===============
>
>
>
>
>
>
>
>----
>
>HM.AI.REQUIREMENTS
>last updated: 31March 2002
>(this document describes the different requirements for the 
>secondary AI Human Markup Schema specifications of the base HumanML 
>Schema)
>---------------------
>
>
>----------------
>ABSTRACT:
>----------------
>This document specifies goals, requirements, and usage scenarios for 
>the for the Human  Markup Language secondary AI Human Markup Schema.
>
>----------------
>DOCUMENT STATUS:
>----------------
>
>The design of HumanML secondary AI Human Markup Schema is designed 
>to address the broad spectrum of possible AI related applications in 
>which HumanML would play a role.  This Requirements Document  is 
>designed in the expectation that this document, the secondary AI 
>Human Markup Schema, will be modified as needed.
>
>This document is normative as of the date it is adopted by the OASIS 
>HumanMarkup Technical Committee.
>
>----------------
>TERMINOLOGY:
>----------------
>As with the base HumanML Schema, for the purposes of clarity, we 
>offer these definitions for terms we use in general and which may 
>appear in this document but are not specific to this document:
>
>Human Markup Language AI (a compound term with separated words with 
>Upper and Lower case characters as shown) = the XML-based computer 
>networking language AI specification itself and all of its 
>associated modules and sub-specifications.
>
>HumanML.AI(compound term with Upper and Lower case characters as 
>shown) = the Human Markup Language AI Specification.
>
>HumanMarkupAI (compound term with Upper and Lower Case characters as 
>shown) = the collective effort to build the Human Markup Language AI 
>sub-specification, also used for similar purposes in the name of the 
>OASIS HumanMarkup Technical AI Sub-Committee.
>
>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 interpretated as described in 
>RFC 2119. ref.: http://www.ietf.org/rfc/rfc2119.txt
>
>"HumanAI"
>
>When enclosed in double quote marks, as above, it is used as a name 
>for what the HumanMarkup AI sub-Initiative aims to encapsulate into 
>HumanML.AI. Used thus, this term transcends reference to any single 
>biological entity's or to the collective biological species of Homos 
>Sapiens simulation of cognitive function, and is inclusive of all 
>self- to species-conscious effort throughout our history to 
>understand ourselves and our cognitive processes.
>
>"Must"
>When enclosed in double quote marks, as above, this word, means that 
>the requirement item has been classified as an absolute requirement.
>
>"Should"
>When enclosed in double quote marks, as above, this word means that 
>it is believed by this Technical Committee that the requirement item 
>will prove itself as absolute in the future, but has not yet been 
>classified as such and may be overridden by another requirement.
>
>"May"
>When enclosed in double quote marks, as above, this word means that 
>the requirement item can become a requirement in the future, but 
>further study is needed.
>
>
>----------------
>CLASSIFICATION:
>----------------
>Secondary Schemata (Was: vocabularies)
>
>This document classifies the secondary AI "module" as a Secondary 
>Schema of the Primary HumanML Schema on an equal footing with all 
>other Secondary Schemata as being capable of engendering and 
>containing further modules which can be classified as derivative or 
>submodules as appropriate, but which may always be seen as existing 
>in the Secondary grouping on an equal footing.
>
>----------------
>EXISTING STANDARDS:
>----------------
>The AI community in concert with the Internet community is 
>attempting to derive useful crossover applications. This naturally 
>leads to potential overlap among developing AI-Internet standards.
>
>HumanMarkupAI standards "must" always be based on the most widely 
>accepted, non-proprietary standards available. At this time this is 
>XML, http://www.w3.org/TR/REC-xml
>
>The Human Markup Language AI specification "should" not attempt to 
>produce new standards in relation to informational subject or topic 
>areas already addressed or covered by the above-referenced most 
>widely accepted standards.
>
>HumanML.AI "should"  incorporate and/or provide for interoperabiity 
>with the above-referenced most widely accepted developing standards 
>(or pseudo standards), such as RuleML, DAML+OIL, and the Artificial 
>Intelligence Markup Language (AIML), but allow for extensibility.
>
>HumanML.AI "should" use the most effective standards, protocols and 
>methodologies available to encapsulate what is "HumanAI" in a well 
>formed data wrapper.
>
>----------------
>REQUIREMENTS:
>----------------
>HumanML.AI "must" be open, which means readily available in its 
>whole and its parts without recourse to restricted access by any 
>criteria.
>
>HumanML.AI "must" be non-proprietary, which means that no private 
>ownership may be asserted over its whole or its parts and it must 
>also be unencumbered by any pre-existing Intellectual Property 
>Rights for its whole or any part of its specifications.
>
>HumanML.AI "must" be public, which means available freely and 
>without any charge added to the cost of transmission to anyone by 
>common means such as the World Wide Web or International Postal 
>Services.
>
>HumanML.AI "must" be standard, which means that it is uniform in its 
>whole and its parts with regard to any and all applications which 
>make use of it.
>
>HumanML.AI " must " be vendor and/or platform neutral.
>
>----------------
>COMPATIBILITY:
>----------------
>HumanML.AI " must " conform to XML syntax and rules.
>
>----------------
>EXTENSIBILITY:
>----------------
>HumanML.AI Schema "must" be extensible.
>
>Terseness "should" be preferred.
>
>
>----------------
>INTERNATIONALIZATION:
>----------------
>Since XML is Unicode, HumanML.AI implementations "must" support this 
>by default and in a well-defined syntax. This section will most 
>likely span a "syntax guidelines rule " applicable to the HumanML.AI 
>module for a common syntax definition.  (This requirement will 
>reflect how syntax inclusion is handled by the base HumanML 
>specification. )
>
>
>----------------
>TRUST/DIGITAL SIGNATURES:
>----------------
>HumanML.AI, and the HumanMarkupAI "should" take into account issues 
>of trust, digital signatures, and privacy.
>
>(Note: This requirement will reflect how HumanML in general handles 
>the issues of trust, digital signatures, and privacy)


--