Re: [docbook-tc] assembly metadata container

[Scott Hudson <scott.hudson@flatironssolutions.com>]

I think I like the info-merge suggestion. I don't like info-override, 
and I think info-resource might get confusing.

We could call it infomerge or infoMerge too, if that's the style. I 
don't have major heartburn with hyphens in element names.  I think I 
prefer camel-case, but we haven't used that traditionally either...

--Scott

On 22-Feb-10 10:25 AM, Bob Stayton wrote:
> I'm following up on my action item from the last DocBook TC. We agreed that<info>
> would be used in assembly elements to document the assembly element that contains the
> info, which follows the current usage of info in DocBook. We agreed that any override
> information that would be used when a resource is used in a module when it is
> assembled should be in another container element within module.  We need to decide on
> the name of that container now.  The three suggestions from the meeting were:
>
> 1.  info in a different namespace
>
> 2.  info-override
>
> 3.  info-resource.
>
>
> I'll add one more:
>
> 4.  info-merge, to indicate this info is applied when topics are merged into a
> document.
>
>
> I'll make one observation on naming style: currently DocBook has no elements with
> hyphens in the name.  There is certainly no rule against it, but I thought I would
> point out that fact.
>
> Bob Stayton
> Sagehill Enterprises
> bobs@sagehill.net
>
>
>
> ---------------------------------------------------------------------
> 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
>
>