Are you suggesting or even hinting that it should be possible
to define a type whose contents are types rather than elements?
e.g something like this should be possible
<xsd:complexType name="appliance-type">
<xsd:sequence>
<xsd:complexType ref="model-number-type" />
...
</xsd:sequence>
</xsd:complexType>
or
<xsd:complexType name="appliance-type">
<xsd:sequence>
<xsd:type ref="model-number-type" />
...
</xsd:sequence>
</xsd:complexType>
----
Stephen D Green
On 11 March 2011 20:55, Costello, Roger L. <> wrote:
> Hi Folks,
>
> Is there a difference between abstraction and reuse?
>
> Suppose I observe that all appliances have a model number, a description, and a warranty. Subsequently I create this complexType:
>
> <xsd:complexType name="appliance">
> <xsd:sequence>
> <xsd:element name="model-number" type="xsd:ID"/>
> <xsd:element name="description" type="xsd:string"/>
> <xsd:element name="warranty" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
>
> Is that complexType an abstraction?
>
> It is clearly a reusable thing. But I am not convinced that it is an abstraction because it is hardcoded to specific element names. What do you think?
>
> Do you think that we (the XML community) have powerful mechanisms for creating abstractions? If not, what is missing? If yes, please provide an example of a powerful abstraction that you have created or you have seen created. What makes it powerful?
>
> /Roger
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe:
> subscribe:
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>
