SingleItemSubmission1 DTD

RegRep folks,

Earlier this week I proposed to the other implementors in RegRep that we
focus on the simplest case first, i.e. how does a Submitting Organization
(SO) submit the metadata for a single XSGML-entity to a Registration
Authority for registration.  I volunteered to produce a simple Submission
DTD for that purpose.

First lets make a distinction among terms:  An XSGML-entity is an item to
be registered, a <data-element> is metadata about the XSGML-entity to be
registered, and an <xsgml-entity-reference> is a pointer to the actual
XSGML-entity instance.  A Registry will maintain the metadata about an
XSGML-entity, including a reference to its instance (which may or may not
be at the same location) and a Repository will maintain the instance
itself. A Registry/Repository will do both.

My first proposal is for a "vanilla" submission that is completely self
contained.  That is, the XSGML-entity to be registered does not have any
Associations with other XSGML-entities and has no Related Data instances.

Attached is a text file, SingleItemSubmission1, for that DTD, along with an
identical file having a "dtd" file extension appropriate for various XML
tools to parse and present.

The DTD is complete with 20+ "Semantic Rules" identifying the purpose of
each XML element and any semantic restrictions on its values.  I'd
appreciate any comments on either the DTD itself or its Semantic Rules. It
is not a complete subset of DTD's currently specified because it singles
out <xsgml-entity-reference> for special attention, adds the concept of
<local-reference-name>, and adds two new attributes for <contact>s.  

While the rest of you contemplate "SingleItemSubmission1", I'll work on an
extension, call it SingleItemSubmission2 that supports both Associations
and Related Data.  Then, if those two items make sense, we can consider the
more difficult task of deciding definitions for and relationships among
data element dictionaries, containers, packages, etc.

-- Len G.