dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Questions emerging in the review of the metadata element
- From: Kristen James Eberlein <kris@eberleinconsulting.com>
- To: DITA TC <dita@lists.oasis-open.org>
- Date: Mon, 17 Jan 2022 18:45:32 -0500
Hi, folks.
There are a lot of questions emerging in the review of the
metadata elements. I'm going to create a list of items that we
might want to discuss on the TC call. In no particular order:
- This element (series|brand|author|etc.)Â does not take the
@keyref attribute. Why not? And why is @keyref available on
<publisher>?
- Why are we mentioning where an element is equivalent to Dublin
Core? Shall we remove this information? Cross reference the
Dublin Core spec?
- Is there an interaction between certain elements (audience,
platform, product) and the similarly-named attribute?
- @content on <othermeta> holds translatable content.
Should we fix this for DITA 2.0?
- Why don't we mention anything about processing for this
element? It only seems to be useful IF you build specialized
processing ...
- General puzzlement about the original design of these
elements, which reflect usage within IBM circa 2000-ish ...
I confess, I don't usually use many of these elements, nor have
implementations that I've designed.
My personal usage (and OOB usage for implementations):
- <author>
- <category>
- <copyright>
- <keywords>
- <metadata>
- <othermeta>
I've certainly specialized a lot of metadata elements for
clients. The use cases for specialized metadata elements usually
are the following:
- Need to store metadata from a legacy system
- Particular requirements for a portal, viewing system,
print/PDF output
--
Best,
Kris
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]