Re: Passing #FIXED values through para. entity refrences
Amit Rekhi (amitr@abinfosys.com)
Thu, 30 Jul 1998 19:16:01 +0530
This is a multi-part message in MIME format.
------=_NextPart_000_0144_01BDBBEE.7D542900
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Martin ,
>Unfortunately there is currently no standardized mechanism for passing
>parameters to default attribute values.
Is there no other way (except parameter passing), that can solve the =
problem
of encapsulating two attribute declarations (which are identical except =
for
their fixed default values) in one entity?
(The reason I thought there could be one was because if it makes sense =
to
encapsulate something which is 100% identical , then something which is =
90%
same (except for the fixed default values) should also be a possible
candidate for encapsulation.)
A new proposal for
>the modularization of SGML DTDs through entity references may make this
>possible later, but not for the time being in XML.
Is any such proposal being worked on?If so when is it expected?
Is there any formal documentation of DTD modularization and compaction
techniques you would be knowing of?
Thanking You,
AMIT
>Amit
>
>Unfortunately there is currently no standardized mechanism for passing
>parameters to default attribute values. When fixed values are required =
to
be
>defined in the DTD you must declare them individually. (A new proposal =
for
>the modularization of SGML DTDs through entity references may make this
>possible later, but not for the time being in XML.)
>
>Martin Bryan
>
>
------=_NextPart_000_0144_01BDBBEE.7D542900
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
Martin ,
>Unfortunately there is currently no =
standardized=20
mechanism for passing
>parameters to default attribute =
values.
Is=20
there no other way (except parameter passing), that can solve the =
problem
of=20
encapsulating two attribute declarations (which are identical except=20
for
their fixed default values) in one entity?
(The reason I =
thought=20
there could be one was because if it makes sense to
encapsulate =
something=20
which is 100% identical , then something which is 90%
same (except =
for the=20
fixed default values) should also be a possible
candidate for=20
encapsulation.)
A new proposal for
>the modularization of =
SGML DTDs=20
through entity references may make this
>possible later, but not =
for the=20
time being in XML.
Is any such proposal being worked on?If so =
when is it=20
expected?
Is there any formal documentation of DTD modularization =
and=20
compaction
techniques you would be knowing of?
Thanking=20
You,
AMIT
<= BR>>Amit
>
>Unfortunately=20
there is currently no standardized mechanism for =
passing
>parameters to=20
default attribute values. When fixed values are required =
to
be
>defined=20
in the DTD you must declare them individually. (A new proposal =
for
>the=20
modularization of SGML DTDs through entity references may make=20
this
>possible later, but not for the time being in=20
XML.)
>
>Martin =
Bryan
>
>
------=_NextPart_000_0144_01BDBBEE.7D542900--
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)