@scale on <table> and <simpletable>

To the best of my memory, @scale is not part of the OASIS table model. (Robert, can you check? https://www.oasis-open.org/specs/tm9901.htm)

We decided at last week’s TC meeting to open a “cleanup” item to make the values currently allowed for @scale on <image> also the values allowed on <fig>, <pre>, and specializations of <pre>. We did not make any decision about @scale on <table> or <simpletable>.

Gershon, I’ll add this to the agenda for today’s TC call.

Best,

Kris

From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> On Behalf Of Gershon Joseph
Sent: Tuesday, June 7, 2022 5:45 AM
To: Nancy Harrison <nharrison@infobridge-solutions.com>; dita@lists.oasis-open.org
Subject: RE: [dita] Groups - DITA TC Meeting Minutes 31 May 2022 uploaded

***ActionItem: Robert will open issue for doing this as part of cleanup work.
- Gershon; if OASIS Exchange table doesn't have @scale, we may want to treat them the same as everything else.
- Robert; I'm not willing to fully endorse that based on 4 mins of googling.

I thought we asked Robert to research table & simpletable and let us know if the scale attribute is from the OASIS Exchange content model or not. If @scale is there because of the OASIS Exchange table model then we keep it as-is. If it was added to the DITA spec independently of the OASIS Exchange table model, we need to discuss what we do with it for DITA 2.0.

Cheers,

Gershon

Unlock the Knowledge in Your Enterprise™

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please notify us by return email if you have received this email in error. © 2022, Precision Content Authoring Solutions Inc. Toronto, Ontario, Canada

gershon joseph senior information architect
180 John St. Toronto, ON Canada M5T 1X5 T: (647) 557-5965 gershon@precisioncontent.com
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please notify us by return email if you have received this email in error. ©2022, Precision Content, Toronto, Ontario, Canada

From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> On Behalf Of Nancy Harrison
Sent: Monday, June 6, 2022 11:39 PM
To: dita@lists.oasis-open.org
Subject: [dita] Groups - DITA TC Meeting Minutes 31 May 2022 uploaded

Submitter's message
ActionItems:
1. Robert will open issue for clarifying @scale usage as part of cleanup work.
2. Stan will turn the OASIS DITA TC Membership Inventory list into a wiki page.
3. Kris will ping Bill Burns who recently moved to HP, about rejoining TC.
4. Scott will mine dita-users list for possible TC members.

=================================================
Minutes of the OASIS DITA TC
Tuesday, 31 May 2022
Recorded by Hancy Harrison
link to agenda for this meeting:
https://wiki.OASIS-open.org/dita/PreviousAgendas

Attendance:
===========
Robert Anderson, Carsten Brennecke, Stan Doherty, Kris Eberlein, Nancy Harrison, Scott Hudson, Gershon Joseph, Zoe Lawson, Keith Schengili-Roberts, Eric Sirois, Dawn Stevens, Frank Wegmann, Jim Tivy

Business
========
1. Roll call
Regrets: (last 30 minutes of call) Gershon Joseph, Keith Schengili-Roberts

2. Approve minutes from previous business meeting:
24 May 2022
https://lists.oasis-open.org/archives/dita/202205/msg00025.html (Harrison, 26 May 2022)
Kris moved, 2nd by Eliot, approved by TC

3. Announcements: none

4. Action items
23 November 2021:
Scott: Pursue possibilities of using Syncrosoft tooling for reviews
15 February 2022:
Eliot: Develop example for using object element for an iFrame
10 May 2022:
Stan: To look through OASIS rosters and develop list of companies for use in recruiting to the TC COMPLETED
24 May 2022
Kris: Respond to Stefan Eike on dita-comment COMPLETED
Kris: Add Eike item to list for consideration for DITA 2.1 COMPLETED
Kris: Contact Mike Iantosca re: Avalara participation in DITA TC
Kris or Robert: Add removing title attr from reltable to list of DITA 2.0 bug fixes COMPLETED
- Kris; TC health items are on agenda.

5. Review of DITA 2.0 proposal deadlines
https://wiki.oasis-open.org/dita/DeadlinesDITA2.0
- Kris; no updates on my proposals; #647 is on agenda today; we need a date from Robert for proposal on adding new @.
- Robert; probably not this week, aiming for next week, probably Friday; ask me again later this week.
- Kris; so possibly on 6/10.

6. (Continued) Scale attribute
https://lists.oasis-open.org/archives/dita/202205/msg00006.html (Stevens, 12 May 2022)
- Kris; we hed this open for Robert. From Dawn's email from client. We've agreed that @scale on video is impractical/not useful. But also, @scale isn't defined consistently. Is there a rationale for that? And can we call the fix just a bug fix?
- Robert; it's not a bug, but I don't remember the history of it. I think, the inconsistency is around its definition on tables as well, wrt CALS tables. But I don't remember why it was done this way for preformatted elements.
- Dawn; you had said we need a proposal, or do we just need a bug?
- Kris; I think we can treat it as a bug.
- Robert; not a bug, but a 'cleanup item', since it was intentional.
- Kris; any objections to having this be cleanup for 2.0?
[none]
- Dawn; so this would be just for pre-formatted elements but not for table? We need it on table.
- Kris; yes; it's just making it standard between codeblock and other elements specialized from pre.
- Robert; just to be clear, it will apply to everything derived from pre.
- Kris; but the inconsistency still bothers me...
- Robert; I'm a bit confused, I think it was just copied from table. so it affects everything that uses display-atts. It probably made its way in thru simpletable. So, do we want to change all the elements - codeblock, msgblock, lines, and fig?
- Gershon; I'm fine with applying it to all of those, we don't need it for lines.
- Robert; I won't remove it from lines; do we keep it, so restricted values are only around table and simpletable?
- Gershon; do we have OASIS Exchange on simpletable too?
- Robert; for simpletable, we do.
- Gershon; I'm fine for keeping everything consistent, except for table/simpletable.
- Kris; for clarity in spec, let's indicate that @scale on table/simpletable has different values than on other elements. Does that work for you, Robert?
- Robert; I'm not finding @scale defined in OASIS tables.
- Kris; let's do it for non-table items.
***ActionItem: Robert will open issue for doing this as part of cleanup work.
- Gershon; if OASIS Exchange table doesn't have @scale, we may want to treat them the same as everything else.
- Robert; I'm not willing to fully endorse that based on 4 mins of googling.

7. Recruiting new companies and people to the DITA TC
OASIS DITA TC Membership Inventory
https://lists.oasis-open.org/archives/dita/202205/msg00035.html (Doherty, 30 May 2022)
A few corrections: https://lists.oasis-open.org/archives/dita/202205/msg00041.html (Eberlein & Kimber, 31 May 2022)
Venn diagram
https://www.oasis-open.org/committees/download.php/69973/Membership-diagram.pdf (Doherty, 30 May 2022)
- Kris; this topic is based on my concern that we've dropped below critical mass for voting members of TC.
- Scott; looking at the list, Boeing is a OASIS member.
- Keith; AMD bought Xylinks, so Xylinks is now part of an OASIS member, so they're now a member as well.
- Eliot; and Freescale is now in NXP.
- Frank; SAP is same as SAP-SE
- Kris; what would be more useful, a wiki page or spreadsheet? I'm not sure everyone can update a single spreadsheet in the OASIS Kavi repo...
- Zoe; I'd prefer a wiki.
- Keith; also prefer a wiki; it's more accessible, would it be under OASIS?
- Kris; yes.
- Keith; to make this more visible, a wiki is way to go.
- Kris; will someone take an action item to turn this list into a wiki?
- Stan; I'll do it
***ActionItem: Stan will turn the list into a wiki page.
- Kris; I think a list of OASIS member orgs. using DITA are much more than this. also things are fluid.
- Kris; if this goes on a wiki, we need to indicate which companies still exist, have been acquired, sold, bought, etc. It would be useful to annotate the list. For example, some are no longer in DITA space. Some of our work is to figure out which companies have substantial DITA investments, to be targeted to enrolling in OASIS or becoming active, or funding a foundation.
- Stan; should I add your list to the wiki as well, and we can sort it out later?
- Kris; yes.
- Dawn; I just sent a note to my clients at Siemens, who have been sending lots of questions, just to encourage them to send a rep to the TC.
- Kris; wrt group C from the diagram, do folks know any of them
- Dawn; many of them are CIDM members.
***ActionItem: Kris will ping Bill Burns who recently moved to HP, about rejoining TC.
- Nancy; Tetsuya Sekine knows people at Fujitsu.
- Kris; but his individual OASIS membership dropped within the last month...
- Stan; I know some folks at Splint, but they're not using DITA.
- Kris; so we don't want to contact them. I'd like folks to mull this over and think about:
1. what should we talk about?
2. what actions should we be taking?
3. any questions we should pose to prospects?
Also, given folks we know, are there people you'd like to see on the TC as voting members? e.g. Shane Taylor at Cengage? (web-based learning)
**AI: Kris will post to list with her questions: Who would you like on TC? Don't worry for now if they have OASIS memberships.
- Stan; Bob Johnson is interested in joining.
- Kris; He was at Intuitive, noow at Tazoo (?) Any thoughts from others?
- Scott; any active users on dita-users list we could mine?
- Kris; would you take an AI to do that?
- Scott; sure.
***ActionItem: Scott will mine dita-users list for possible TC members.
- Kris; possibly Chris Papademetrious (works at Synopsis, Zoe's company). Also, we should look at look at dita-comment posters.
- Kris; this can't be handled in one meeting, we will float it on/off our agenda.

8. DITA 2.0 stage two proposals
Vote
(Reopened) Issue #647: Remove classification domain and add subjectrefs attribute
https://lists.oasis-open.org/archives/dita/202205/msg00024.html (Eberlein, 26 May 2022)
Kris moved

Voting results:
yes votes 12 (Robert Anderson, Carsten Brennecke, Stan Doherty, Kris Eberlein, Nancy Harrison, Scott Hudson, Gershon Joseph, Zoe Lawson, Keith Schengili-Roberts, Eric Sirois, Dawn Stevens, Frank Wegmann)
no votes 0

9. DITA 2.0 stage three proposals
Feedback
(Continued) subjectrefs attribute
https://lists.oasis-open.org/archives/dita/202205/msg00007.html (Eberlein, 16 May 2022)
https://lists.oasis-open.org/archives/dita/202205/msg00010.html (Kimber, 22 May 2022)

https://lists.oasis-open.org/archives/dita/202205/msg00014.html (Eberlein, 23 May 2022)
https://lists.oasis-open.org/archives/dita/202205/msg00015.html (Kimber, 23 May 2022 -- forwarded to list by Eberlein)
- Eliot; what are implications for usage of scoped keys within this @; for purposes for key resolution?
- Kris; do we need discussion about #1 (from Eliot's 22May email)? The spec is pretty clear about this.
- Eliot; having included SS Map; if it's in a key scope, I'd expect to be able to use scope-qualified keys. If a map is used in peer map, and you want to use it with a scope, you have to be able to.
- Kris; we've done review of subjectScheme (SS) maps, but not around keys/keyrefs.
- Eliot; there shouldn't be a reason to change them in 2.0. but in the specific case of @subjectrefs, which is a list of subjects, subjects are defined with keys in SS maps. The question is whether or not @subjectrefs is a list of refs to keys or to subjects, where a subject is not really a key, but is just defined as one. The way we define them has different implications wrt how I'm defining it; only in context of @subjectrefs do we use different ways of evaluating keys.
- Kris; any thoughts, Robert?
- Robert; we want them to work like keys, so we're stuck with whatever comes with that.
- Kris; whatever we do with this, we need to get class map and domain out of DITA 2.0. What are implications of this, and will we be able to produce a DITA 2.1?
- Eliot; I'm not suggesting anything about removal of those domains.
- Robert; they have to be treated the same way, otherwise we're in a mess of trouble.
- Kris; I'm assuming we treat them as normal keys, doing otherwise might have short-term uses, but it's a terrible way to operate. I wish we'd been able to redo SS for 2.0.
- Eliot; for your stage 3 proposal, I'm happy to contribute thoughts and language to make things clearer.
- Kris; Eliot, will you be an add'l reviewer?
- Eliot; yes.
- Kris; why wouldn't we expect processors to resolve this?
- Eliot; there are situations where an ordinary processor wouldn't be able to support these; e.g., 1. an SS map used as a peer map, 2. in the case where SS map isn't referenced thru ordinary DITA processing. and support for @subjectrefs can't be mandatory.
- Kris; there are no processing expectations for @subjectrefs; we're putting it in only to provide some kind of replacement for class domain.
- Eliot; I just want it to be clear that it may be an expectation, but it isn't a requirements.

10. DITA 1.x to 2.0 migration work to be done
https://lists.oasis-open.org/archives/dita/202205/msg00011.html (Kimber, 22 May 2022)
https://lists.oasis-open.org/archives/dita/202205/msg00020.html (Eberlein, 24 May 2022)
[no update]

11. Volunteer tasks
https://wiki.oasis-open.org/dita/volunteerTasks
[no update]

12. Review tooling
https://lists.oasis-open.org/archives/dita/202111/msg00006.html (Eberlein, 02 November 2021)
https://lists.oasis-open.org/archives/dita/202111/msg00016.html (Hudson, forwarded by Eberlein on 09 November 2021)
Suggestion that reviews of stage 3 proposal for #647 use Content Fusion
- Kris; let's use ContentFusioni to do these upcoming reviews. Any issues?
[none]

12 noon ET close

-- Ms. Nancy Harrison

Document Name: DITA TC Meeting Minutes 31 May 2022

No description provided.
Download Latest Revision
Public Download Link

Submitter: Ms. Nancy Harrison
Group: OASIS Darwin Information Typing Architecture (DITA) TC
Folder: Meeting Notes
Date submitted: 2022-06-06 13:38:48

dita message