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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-sidsc message

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


Subject: 2009-05-13 teleconference recording and notes


For those who couldn’t make today’s call but would like to hear the discussion, the recording is available for playback: 

https://www115.livemeeting.com/cc/freescale/view?id=sidsc-090513 

Additionally, here are the notes I capture in text during the call:

Guiding principle: loosening constraints in later versions of the DTD incurs
less risk for backward compatibility than adding tighter constraints; therefore
we should err on the side of being more constrained when possible.

____________________

D3 p. 63. registerPropset. Annette notes that all elements contained within
registerPropset are shown to have an instance of ONE. However, for
addressOffset: We sometimes have more than one address associated with a
register (a separate address for each access type). For registerResetValue: we
sometimes don't provide a reset value at the register level.
We need to verify whether we need to change the DTD. Here are 2 use cases
requiring more than one or less than one.

RECOMMENDATION: we should define several use cases, and implement each to prove
the model.

Seth (offline): multiple arrays are supported by the dimension attribute ... is
that adequate?

>> actions: retrofit unresolved comments from D3 to D4, break this one out to
new email thread, each member to gather UC examples.

____________________

D3 p. 78. bitFieldPropset. Is the bitFieldAccess field required? We don't always
identify the access type at the bit level.

>> actions: verify that the data model fully supports both use cases (specify
access for all fields at the register level, or specify / override access at the
bit field level). (Tom Cihak)

____________________

D3 p. 84. bitFieldAccess. Annette: Are we restricted to the values defined here?
(Does DITA check?) I think there's at least one more possibility for a reserved
field (I'll have to verify.)
Bob: We are not restricted and DITA is not going to check. This would have to be
tool enforcement. Annette needs to check and let us know about whether she has
another case for reserved. (I've sent the query to Annette).

>> comment added to D4 PDF ... Annette to forward her added possible values to
the dita-sidsc list.

Respectfully,
Bob Beims

Chair, DITA TC SIDSC

Applications Engineer, Staff Principal
Microcontroller Solutions Group

Freescale Semiconductor, Inc.
6501 William Cannon Drive West, MD: OE49    
Austin, TX 78735-8598

www.freescale.com
bob.beims@freescale.com

This e-mail, and any associated attachments have been classified as:
[X]Public
[ ]Freescale Semiconductor Internal Use Only
[ ]Freescale Semiconductor Confidential Proprietary



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