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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-lightweight-dita message

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


Subject: Re: [dita-lightweight-dita] Does <data> need @href?


Gently pushing back on this ... if "is it in DITA 1.3?" were the test for inclusion in Lw-DITA, well ...

What can an @href attribute accomplish that @name/@value cannot? I acknowledge that @href has processing implications in full DITA. If that's the driving requirement here, I can accept that. But (generally), if one can meet a requirement in Lw-DITA with more general/extensible markup (in this case, @name/@value), I would favor punting the more specific markup.

-Alan


On 3/30/17 11:14 AM, Mark Giffin wrote:
Thanks Ian. <data> has @href in DITA 1.3 also, so I'll leave it as it is in lwdita.

Mark

On 3/30/2017 2:10 AM, ian bd wrote:
Yes, if <data> is used for recording metadata about the topic. I have a need -- and I am sure I am not the only one doing this sort of thing -- to record references used for a topic, including websites. That recording is carried out using <data> in the <prolog> and @href is the natural (hesitate to say semantic) attribute to hold the information for internal use.

Ian

On Thu, Mar 30, 2017 at 6:07 AM, Mark Giffin <mark@markgiffin.com> wrote:
Another question based on the sharp eyeballs of Scott Prentice: <data> has an @href attribute, this seems like a mistake. Do we need it?

Thanks,
Mark Giffin
Mark Giffin Consulting, Inc.
http://markgiffin.com/


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



-- 
Alan Houser
Group Wellesley, Inc.
Consultant and Trainer, Technical Publishing
arh on Twitter
412-450-0532 


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