OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Fwd: [dita] Fwd: [dita-comment] Limitations for attribute specialization


Another item for tomorrow's TC meeting agenda.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)




-------- Forwarded Message --------
Subject: RE: [dita] Fwd: [dita-comment] Limitations for attribute specialization
Date: Mon, 2 Aug 2021 10:59:20 -0300
From: Rodolfo M. Raya <rmraya@maxprograms.com>
Organisation: Maxprograms
To: 'Kristen James Eberlein' <kris@eberleinconsulting.com>


Hello Kris,

Â

Stefan is also suffering from a problem I mentioned before regarding RelaxNG grammars: default values are not retrieved by Java parsers.

Â

Stefan created a new element and set its default @translate value to ânoâ, something I consider OK. His files are valid XML and declare the RelaxNG grammar at the top. When the Java parser reads his file, it does not set the @translat attribute to ânoâ when it is implicit and the element is exposed for translation.

Â

I know that Oxygen team had to write their custom way to deal with this. I donât use the Open Toolkit and I donât know how it handles default attribute values, but I suspect that a similar issue may happen. I will review the OT code looking for a custom parser that I can reuse, but I donât have much hope.

Â

Perhaps you didnât know, but the default catalog handler shipped with Java 11 chokes with DITA catalogs. It expects absolute URIs in @xml:base attributes and DITA catalogs have relative values instead. I have already written my own catalog manager to solve this.

Â

So, back to the point that makes me write this message: I will have to write my own parser for RelaxNG grammars and I accept that, but the DTIA TC should seriously consider available frameworks when releasing new versions.

Â

Regards,

Rodolfo

--

Rodolfo M. RayaÂÂÂ ÂÂ rmraya@maxprograms.com

MaxprogramsÂÂÂÂ Âhttps://www.maxprograms.com

Â

From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> On Behalf Of Kristen James Eberlein
Sent: Monday, August 2, 2021 10:32 AM
To: DITA TC <dita@lists.oasis-open.org>
Subject: [dita] Fwd: [dita-comment] Limitations for attribute specialization

Â

FYI; I'll put this on tomorrow's TC meeting agenda.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)



-------- Forwarded Message --------

Subject:

[dita-comment] Limitations for attribute specialization

Date:

Mon, 14 Jun 2021 11:49:37 +0000

From:

Stefan Eike <Stefan.Eike@dometic.com>

To:

dita-comment@lists.oasis-open.org <dita-comment@lists.oasis-open.org>




Dear honourable DITA committee,

Â

Iâve added a new attribute (type) to a specialized element. This attribute is not specialized, itâs just added as shown below. My question now is: âIs this allowed?â I mean, technically this is no problem and this can be processed with the DITA-OT and the PDF2 plugin (and others). Iâve read these sections: Overview of specialization, Specialization rules for attributes, RELAX NG: Coding requirements for attribute domain modules

Â

I could not find a statement saying something like âIf you add an attribute, it must be added as a âspecializedâ attributeâ. Do I violate the specification and should I feel bad?

Â

<define name="tv.attributes">
ÂÂÂ
<ref name="univ-atts-translate-no"/>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="name" a:defaultValue="tv"/>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="datatype"/>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="value"/>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="href"/>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="keyref"/>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="format"/>
ÂÂÂ
</optional>
ÂÂÂ <attribute name="type">
ÂÂÂÂÂÂÂ
<choice>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>A</value><a:documentation>Ampere</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Ah</value><a:documentation>Ampere hour</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Bq</value><a:documentation>Becquerel</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>F</value><a:documentation>Farad</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Gy</value><a:documentation>Gray</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>H</value><a:documentation>Henry</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Hz</value><a:documentation>Hertz</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>J</value><a:documentation>Joule</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>K</value><a:documentation>Kelvin</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>L</value><a:documentation>Liter</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>N</value><a:documentation>Newton</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Pa</value><a:documentation>Pascal</a:documentation>
ÂÂÂ ÂÂÂÂÂÂÂÂ
<value>S</value><a:documentation>Siemens</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Sv</value><a:documentation>Sievert</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>T</value><a:documentation>Tesla</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>V</value><a:documentation>Volt</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>W</value><a:documentation>Watt</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Wb</value><a:documentation>Weber</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>bar</value><a:documentation>Bar</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>cd</value><a:documentation>Candela</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>cm</value><a:documentation>Centimeter</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>cmÂ</value><a:documentation>Square Centimeter</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>dB(A)</value><a:documentation>A-weighted decibels</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>g</value><a:documentation>Gram</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>g/h</value><a:documentation>Gram per hour</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>h</value><a:documentation>Hour</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>kWh</value><a:documentation>Kilowatt-hour</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>kat</value><a:documentation>Katal</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>kg</value><a:documentation>Kilogram</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>km</value><a:documentation>Kilometer</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>km/h</value><a:documentation>Kilometer per hour</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>lm</value><a:documentation>Lumen</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>lx</value><a:documentation>Lux</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>m</value><a:documentation>Meter</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>mm</value><a:documentation>Millimeter</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>mmÂ</value><a:documentation>Square Millimeter</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>mol</value><a:documentation>Mole</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>rad</value><a:documentation>Radian</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>s</value><a:documentation>Second</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>sr</value><a:documentation>Steradian</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>t</value><a:documentation>Ton</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Â</value><a:documentation>Degree</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>ÂC</value><a:documentation>Degree Celsius</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Î</value><a:documentation>Ohm</a:documentation>
ÂÂÂÂÂÂÂ
</choice>
ÂÂÂ
</attribute>
ÂÂÂ
<attribute name="sign" a:defaultValue="+">
ÂÂÂÂÂÂÂ
<choice>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>+</value><a:documentation>Plus (positive number)</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>â</value><a:documentation>Minus (negative number)</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>Â</value><a:documentation>Plus-Minus</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>&lt;</value><a:documentation>Lower-than</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
<value>&gt;</value><a:documentation>Greater-than</a:documentation>
ÂÂÂÂÂÂÂ
</choice>
ÂÂÂ
</attribute>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="show-unit" a:defaultValue="yes">
ÂÂÂÂÂÂÂÂÂÂÂ
<choice>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>yes</value>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>no</value>
ÂÂÂÂÂÂÂÂÂÂÂ
</choice>
ÂÂÂÂÂÂÂ
</attribute>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="system" a:defaultValue="si">
ÂÂÂÂÂÂÂÂÂÂÂ
<choice>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>si</value><a:documentation>International System of Units</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>imperial</value><a:documentation>Imperial System</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>si+imperial</value><a:documentation>SI + Imperial</a:documentation>
ÂÂÂÂÂÂÂÂÂÂÂ
</choice>
ÂÂÂÂÂÂÂ
</attribute>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="scope">
ÂÂÂÂÂÂÂÂÂÂÂ
<choice>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>external</value>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>local</value>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>peer</value>
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
<value>-dita-use-conref-target</value>
ÂÂÂÂÂÂÂÂÂÂÂ
</choice>
ÂÂÂÂÂÂÂ
</attribute>
ÂÂÂ
</optional>
ÂÂÂ
<optional>
ÂÂÂÂÂÂÂ
<attribute name="outputclass"/>
ÂÂÂ
</optional>
</define>

Â

Â

Thanks a lot in advance

Stefan

Stefan Eike
Head of Technical Documentation

Phone +49 (0)2572 879 279 Cell +49 (0) 172 8843770
Stefan.Eike@dometic.com

Dometic Germany Holding GmbH â BetriebsstÃtte Emsdetten, Hollefeldstr. 63, 48282 Emsdetten Germany

dometic.com





NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender by reply email and destroy the original message.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]