One of my clients uses Zoomin and Ixiasoft. Ixiasoft has a nice implementation that ingests the subject scheme map and presents it to the users as a taxonomy hierarchy that users use to drag and drop taxonomy terms to
be applied to a map and/or topic. We don’t let writers loose on the subject scheme map, that’s only for the admin who managers the file.
I suspect in the short term removing the classification map and domain from the spec won’t change how our vendors manage this. It may result in custom proprietary mechanisms to manage taxonomies in the future. I’m on
the wall on this one. Let’s see if anyone else responds.
Gershon
Gershon Joseph | Senior Information Architect | Precision Content
Direct: +972 (54) 658-3887| Email: gershon@precisioncontent.com |
www.precisioncontent.com
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. ©2021,
Precision Content Authoring Solutions Inc, Toronto,
Ontario, Canada
From:
dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Kristen James Eberlein <kris@eberleinconsulting.com>
Date: Thursday, 9 December 2021 at 21:19
To: DITA TC <dita@lists.oasis-open.org>
Subject: [dita] Considerations for removing classification map and classification domain
I want us to think about removing the classification map and the classification domain. We'd move them into the new GitHub repo.
Reasons for removing the classification map and domain:
-
It's impossible for authors to use.
-
I don't think anyone uses it, except perhaps Zoomin behind the scenes. For the most part, Zoomin has implementations create a speadsheet which they then build classification maps from, I think.
-
We have the idiocy of shipping the classification domain in the base, but it's only integrated in the technical content shell for map.
Reasons for NOT removing the classification map and domain:
-
It's the only standard-defined mechanism for associating subjects with <topicref> elements
One possibility would be adding an attribute to <topicref> elements, let's call it @subjectrefs, but that would be yet another abuse of how keys work. We'd need to explicitly define what we would expect processors to do when they encountered a @subjectrefs
attribute.
Thoughts?
--
Best,
Kris
--------------------------------------------------------------------- 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