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: SIDSC specialization element naming question

TC Members;

On this morning's Semiconductor Information Design Subcommittee (SIDSC) teleconference, we realized that we may have a conflict with an element naming convention we're moving toward. We'd like the guidance of the TC in avoiding problems.

If you'll take a look at the spreadsheet @ http://www.oasis-open.org/apps/org/workgroup/dita-sidsc/download.php/26033/semi_registers_07Nov2007.xls you'll see a structural / domain information type specialization we're working on to describe semiconductor memory maps, registers and bit fields. We've borrowed heavily from the IP-XACT 1.2 schema for this structure, as a key goal of the specializations for this information type is to interchange data with IP-XACT data sets.

The IP-XACT folks have chosen to define a "name" element that is a required sub-element of several other elements. Since DITA 1.1 defines a @name attribute, are we going to slam into problems if we create a specialized _element_ called "name"?

If you could make sure that your replies include dita-sidsc@lists.oasis-open.org in the cc field, I'd appreciate it (I have the main TC traffic filtered to a folder that I rarely look at).

Thanks in advance for your help,

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