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] Confusing descriptions of lockmeta in DITA 1.2 Spec: CD04,PDF (DITA1.2-spec.pdf)


  Bruce,

Thanks for that clarification - the differing points of view is 
certainly part of the problem. I think it would be a good candidate for 
clarification by the Adoption TC.

Best regards,

Doug Morrison
Information Architect
http://dita4all.com


On 28/09/2010 15:32, Bruce Nevin (bnevin) wrote:
> Doug, FWIW, this is my understanding. From the point of view of the map,
> by default (lockmeta="yes") the metadata in the map is 'locked' so that
> any different metadata attribute-value pair in a referenced topic is
> ignored. From the point of view of the referenced topic, values in the
> map override (if the same attribute is set in both places) or supplement
> (if it is set in the map but not in the topic). The confusion may be
> that from the point of view of the topic lockmeta="yes" means the
> topic's metadata values are not locked. As to bookmeta, etc., they
> behave like the element they are specialized from.
>
> Documentation from the DITA Adoption TC may help to clear this up, but
> as Kris says changes to the spec will have to wait until after DITA 1.2.
>
> 	/BN
>
>> -----Original Message-----
>> From: Doug Morrison [mailto:dmorrison@dita4all.com]
>> Sent: Tuesday, September 28, 2010 8:35 AM
>> To: dita@lists.oasis-open.org
>> Subject: [dita] Confusing descriptions of lockmeta in DITA
>> 1.2 Spec: CD04, PDF (DITA1.2-spec.pdf)
>>
>>
>>    In my view, the various descriptions of the lockmeta
>> attribute are confusing in DITA 1.2 Spec: CD04, PDF
>> (DITA1.2-spec.pdf).
>>
>> In Section 3.1.2.1.2 'Metadata in maps and topics' on pdf p38 it says:
>>
>> quote
>> By default, metadata in the map supplements or overrides
>> metadata that is specified at the topic level, unless the
>> @lockmeta attribute of the<topicref>  element is set to "no".
>> endquote
>>
>> In the default situation, what determines whether metadata is
>> supplemented or replaced?
>>
>> I take it that the default is for lockmeta="yes" or lockmeta
>> is absent.
>>
>> Whatr if lockmeta is present on topicmeta, subjectHead or bookmeta?
>>
>> I think "<topicref>" should be replaced by"<topicmeta>",
>> because in Section 3.1.2.1.2, 'topicref' there is no mention
>> of lockmeta attribute.
>>
>>
>> In Section 3.1.2.1.3, 'topicmeta' the description of lockmeta is
>>
>> quote
>> Indicates whether any of the meta
>> information should be replaced by meta
>> information in the referenced topic. If the
>> value is yes, the information inside
>> <topicmeta>  should not be replaced with
>> information from the topic.
>> endquote
>>
>> Now the sense of the replacement is reversed. The "If" is ambiguous -
>> does it mean "If and only if"?
>> When is metadata supplemented?
>>
>> Apologies for the lateness of these comments.
>>
>> Regards,
>>
>> Doug Morrison
>> Information Architect
>> http://dita4all.com
>>
>>
>> On 27/09/2010 19:55, robander@us.ibm.com wrote:
>>> The document revision named DITA 1.2 Spec: CD04, PDF
>> (DITA1.2-spec.pdf) has
>>> been submitted by Mr. Robert Anderson to the OASIS Darwin
>> Information
>>> Typing Architecture (DITA) TC document repository.  This document is
>>> revision #1 of DITA1.2-spec.pdf.
>>>
>>> Document Description:
>>> DITA 1.2 draft (PDF version) for the upcoming CD-04 vote.
>>>
>>> View Document Details:
>>> http://www.oasis-open.org/committees/document.php?document_id=39573
>>>
>>> Download Document:
>>>
>> http://www.oasis-open.org/committees/download.php/39573/DITA1.
>> 2-spec.pdf
>>> Revision:
>>> This document is revision #1 of DITA1.2-spec.pdf.  The
>> document details
>>> page referenced above will show the complete revision history.
>>>
>>>
>>> PLEASE NOTE:  If the above links do not work for you, your
>> email application
>>> may be breaking the link into two pieces.  You may be able
>> to copy and paste
>>> the entire link address into the address field of your web browser.
>>>
>>> -OASIS Open Administration
>> ---------------------------------------------------------------------
>> 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_workgr
>> oups.php
>>
>>
> ---------------------------------------------------------------------
> 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]