xml-dev - Re: Questions on DCD

["Jeff Greif" <jmg@trivida.com>]

I'm not familiar with details of DCD, but based on what I see below, I think
this might work:

<ElementDef Type="Kid">
 <Element>Mother</Element>
 <Element>Father</Element>
</ElementDef>

<ElementDef Type="Mother">
 <Element>Person</Element>
</ElementDef>

<ElementDef Type="Father">
 <Element>Person</Element>
</ElementDef>

<ElementDef Type="Person">
 <Element>Name</Element>
 <Element>Address</Element>
</ElementDef>

This is very similar to what you might put in a DTD:
<!Element kid (mother,father)>
<!Element mother (person)>
<!Element father (person)>
<!Element person (name, address)>

Jeff

-----Original Message-----
From: Maneesha Jain <Maneesha.Jain@Ebay.Sun.COM>
To: Maneesha.Jain@Ebay.Sun.COM <Maneesha.Jain@Ebay.Sun.COM>;
Curt.Arnold@hyprotech.com <Curt.Arnold@hyprotech.com>
Cc: xml-dev@ic.ac.uk <xml-dev@ic.ac.uk>
Date: Wednesday, January 20, 1999 1:54 PM
Subject: RE: Questions on DCD


>Hi Arnold,
>
>Thanks for the response. I guess I was looking for a way to represent
following
>java class in DCD syntax.
>
>In java-->
>
>class Kid
>{
> Person mother;    *****
> Person father;
>}
>
>In DCD -->
>
><ElementDef Type="Kid">
> <Element>Person</Element>
> <Element>Person</Element>
></ElementDef>
>
><ElementDef Type="Person">
> <Element>Name</Element>
> <Element>Address</Element>
></ElementDef>
>
>What I don't understand is where in DCD can I specify that the "Ist Person"
>information is about the "mother" and "Second Person" information is about
>"father". In concept, I was looking for a way to specify the "type" and
"name"
>for a <Element> just like in java definition marked as (*****).
>
>Regards,
>Maneesha
>
>>
>> >>1)
>> >>If I define an ElementDef type "A", and then a ElementDef type "B"
>> >>which could contain two elements/members of type A. How do I define
that
>> ?Question 1:
>>
>> What you appear to want to do is something equivalent to a (A,A) content
in
>> the DTD.  You would do this (approximate syntax).  (This requires you to
>> have two A's)
>>
>> <ElementDef Type="B">
>> <Group RDF:Order="Seq">
>> <Element Name="A"/>
>> <Element Name="A"/>
>> </Group>
>> </ElementDef>
>>
>> If you could have 0 or two A (A,A)+, you would do
>>
>> <ElementDef Type="B">
>> <Group RDF:Order="Seq" Occurs="Optional">
>> <Element Name="A"/>
>> <Element Name="A"/>
>> </Group>
>> </ElementDef>
>>
>> I don't believe there is a way to restrict content to 0,1, or 2.  The
best
>> you could do is allow 0 or more A's (A*) have have to limit it in your
>> processor
>>
>> <ElementDef Type="B">
>> <Group RDF:Order="Seq" Occurs="ZeroOrMore">
>> <Element Name="A"/>
>> </Group>
>> </ElementDef>
>>
>
>
>xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
>(un)subscribe xml-dev
>To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
message;
>subscribe xml-dev-digest
>List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)