<commit_before>mci-dnet-xsd - Implementation of XML Schema Data types
======================================================

## Overview

### Historic Context: Project Lupine

This project represents an effective descendant of a feature of a
project originally named _Lupine_, insofar as extending of the design
for an implementation of XML schema data type structures, as
originally defined within the Lupine project. Lupine was represented
primarily of a set of UML models, defined for a goal of implementing
XML schemas, XMI, MOF, and UML within Common Lisp. Lupine has been
subsequently revised as the set of projects organized under the
'mci-dnet' workspace. 

### Implementation of XML Schema Simple Data types

This system implements a facet-oriented view of XML Schema simple data
types.

Facets in terms of XML schema syntax:

* **cardinality:** finite | countably infinite
* **numeric:** true | false
* **order:** partial | total
* **bounded:** true | false

This sytem defines a number of protocol classes for purpose of
representing those facets of XML schema simple data types. Those
protocol classes are defined as to allow for accurate representation of
XML schema data type definitions, within the Common Lisp
environment. The class precedence list of each protocol class, as a
quality essentially orthogonal to the XML Schema specification, is 
defined as to ensure a manner of semantic accuracy in the definition
of the respective data type definition.


Type Structure in mci-dnet-xsd (draft 1 - incomplete)

_Ed. note: Effectively, the structure of relations of class
definitions represented in the original Lupine  XSD simple data types
design will serve to require a documentation structure other than a
single outline. There should be at least three sets of classes listed:_

* _Protocol classes_ (`protocol-class`)
* _Faceted protocol classes_ (`faceted-class`)
* _Simple type classes_ (`simple-type-class`)

_Architectural Note: This system should endeavor to extend of the
metaobject protocol, in implementation of XML schema data types._

_Architectural Note: This system may also endeavor to establish a
certain semantic homology onto CORBA -- viz a viz CLORB -- as
specifically to define a  generic protocol for marshalling and
unmarshalling of values encoded in syntaxes other than ANSI Common
Lisp. That would be essentially orthogonal to the structures of the
class hierarchy defined in mci-dnet-xsd_

<commit_msg>add doc note, application note<commit_after>mci-dnet-xsd - Implementation of XML Schema Data types
======================================================

## Overview

### Historic Context: Project Lupine

This project represents an effective descendant of a feature of a
project originally named _Lupine_, insofar as extending of the design
for an implementation of XML schema data type structures, as
originally defined within the Lupine project. Lupine was represented
primarily of a set of UML models, defined for a goal of implementing
XML schemas, XMI, MOF, and UML within Common Lisp. Lupine has been
subsequently revised as the set of projects organized under the
'mci-dnet' workspace. 

### Implementation of XML Schema Simple Data types

This system implements a facet-oriented view of XML Schema simple data
types.

Facets in terms of XML schema syntax:

* **cardinality:** finite | countably infinite
* **numeric:** true | false
* **order:** partial | total
* **bounded:** true | false

This sytem defines a number of protocol classes for purpose of
representing those facets of XML schema simple data types. Those
protocol classes are defined as to allow for accurate representation of
XML schema data type definitions, within the Common Lisp
environment. The class precedence list of each protocol class, as a
quality essentially orthogonal to the XML Schema specification, is 
defined as to ensure a manner of semantic accuracy in the definition
of the respective data type definition.


Type Structure in mci-dnet-xsd (draft 1 - incomplete)

_Ed. note: Effectively, the structure of relations of class
definitions represented in the original Lupine  XSD simple data types
design will serve to require a documentation structure other than a
single outline. There should be at least three sets of classes listed:_

* _Protocol classes_ (`protocol-class`)
* _Faceted protocol classes_ (`faceted-class`)
* _Simple type classes_ (`simple-type-class`)

_Additional focus should be made about the set of numeric types
defined in XML Schema Data types. Seperately, a note should be made
with regards to enumerable simple types in XSD__

_Application Note: XML schema data types find a relevance in encoding
of XML schemas, and furthermore in RDF XML_

_Architectural Note: This system should endeavor to extend of the
metaobject protocol, in implementation of XML schema data types._

_Architectural Note: This system may also endeavor to establish a
certain semantic homology onto CORBA -- viz a viz CLORB -- as
specifically to define a  generic protocol for marshalling and
unmarshalling of values encoded in syntaxes other than ANSI Common
Lisp. That would be essentially orthogonal to the structures of the
class hierarchy defined in mci-dnet-xsd_


{'fraction_non_alphanumeric': 0.061635944700460826, 'fraction_numerical': 0.00038402457757296467, 'mean_word_length': 4.959954233409611, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1101209', 'n_tokens_mistral': 1301, 'n_tokens_neox': 1213, 'n_words': 736}