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: RE: [dita] Clarrification of @href/@keyref on <data> element


I always assumed the silence on that point was intentional. Since <dita> is
primarily intended as a basis for specialization, and is ignored by default,
I always thought the implications for @href on a <data> specialization
should be up to whoever was developing the tools to process that
specialization.

Chris

-----Original Message-----
From: Eliot Kimber [mailto:ekimber@rsicms.com] 
Sent: Saturday, April 06, 2013 12:12 PM
To: dita
Subject: [dita] Clarrification of @href/@keyref on <data> element

The 1.2 reference entry for <data> says for the @href attribute:

"Provides a reference to a resource. See The href attribute for detailed
information on supported values and processing implications."

However, I can't find any discussion of what it actually means to have
<data> associated with a resource.

Do we say anywhere?

If not, what is the intended implication? Is the associated resource the
metadata value?

Thanks,

Eliot

--
Eliot Kimber
Senior Solutions Architect, RSI Content Solutions "Bringing Strategy,
Content, and Technology Together"
Main: 512.554.9368
www.rsicms.com
www.rsuitecms.com
Book: DITA For Practitioners, from XML Press,
http://xmlpress.net/publications/dita/practitioners-1/


---------------------------------------------------------------------
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 




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