[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Groups - 13059-MetadataCascadeHtml uploaded
Hi Chris, I originally hadn't considered that case, but when I followed up with Dave Helfinstine about the current PTC implementation, he pointed out this wording in the description of the platform attribute: If no value is specified, but the attribute is specified on an ancestor within a map or within the related-links section, the value will cascade from the closest ancestor. The attribute takes a space-delimited set of values. He indicated that they've taken this to mean values don't cascade/merge within normal section content, and seems to me like an interpretation that will generally fit with user expectations. Of course my mind is tied in the DITA-OT, and I know we don't currently *implement* any cascade / merging within topics, so my focus from the start was really on maps -- the OT creates a new copy of the map with those values cascaded everywhere, something that would rarely or never make sense in the topic body. Probably something good to discuss at our call; if there is general consensus that the cascade value should appear everywhere, then I can probably go along with that. Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit (http://dita-ot.sourceforge.net/) From: Chris Nitchie <chris.nitchie@oberontech.com> To: Robert D Anderson/Rochester/IBM@IBMUS, Cc: dita@lists.oasis-open.org Date: 06/09/2013 11:26 Subject: Re: [dita] Groups - 13059-MetadataCascadeHtml uploaded Sent by: <dita@lists.oasis-open.org> Robert, My only concern with this proposal is that it's limited to maps and topicrefs by virtue of only existing on topicref-atts. But this is a problem within topics, as well, and not just in related-links. Consider: <section platform="mac linux unix"> <p>This section covers unix-based platforms.</p> <note platform="mac">But this note is mac-only.</note> </section> It seems to me that the merge/no-merge specification needs to happen within this topic, and maybe even on the <section> or <p> tag. Unless I'm missing something, the proposal doesn't cover this case. Chris On Jun 7, 2013, at 10:06 AM, Robert Anderson <robander@us.ibm.com> wrote: |---------------------------------------------------| |Document Name: 13059-MetadataCascadeHtml | |Description | |Proposal 13059 for managing how metadata attribute | |values cascade and merge | |(or do not merge) with other values (HTML version) | |Download Latest Revision | |Public Download Link | |Submitter: Mr. Robert Anderson | |Group: OASIS Darwin Information Typing Architecture| |(DITA) TC | |Folder: Drafts | |Date submitted: 2013-06-07 07:06:43 | | | |---------------------------------------------------| Chris Nitchie Oberon Technologies, Inc. 2640 Wildwood Trail Saline, MI 48176 Main: 734.666.0400 Direct: 734.330.2978 Email: chris.nitchie@oberontech.com www.oberontech.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]