From eb622d9330090e85ad1badc28de25116422b7266 Mon Sep 17 00:00:00 2001 From: Robert D Anderson Date: Thu, 6 Apr 2023 17:00:47 -0500 Subject: [PATCH] Remove classification domain from 2.0 #647 --- doctypes/dtd/subjectScheme/catalog.xml | 10 +- doctypes/dtd/subjectScheme/classifyDomain.ent | 43 -- doctypes/dtd/subjectScheme/classifyDomain.mod | 305 ---------- doctypes/rng/subjectScheme/catalog.xml | 10 +- doctypes/rng/subjectScheme/classifyDomain.rng | 532 ------------------ .../base-relationship-tables.ditamap | 1 - specification/common/conref-examples.dita | 22 - specification/langRef/base/subjectCell.dita | 37 -- specification/langRef/base/subjectref.dita | 44 -- specification/langRef/base/topicCell.dita | 37 -- .../langRef/base/topicSubjectHeader.dita | 44 -- .../langRef/base/topicSubjectRow.dita | 32 -- .../langRef/base/topicSubjectTable.dita | 181 ------ specification/langRef/base/topicapply.dita | 55 -- specification/langRef/base/topicsubject.dita | 51 -- .../classification-domain-elements.ditamap | 15 - .../key-definitions-base-elements.ditamap | 1 - ...ons-classification-domain-elements.ditamap | 13 - .../quick-reference/base-elements-a-to-z.dita | 5 - 19 files changed, 2 insertions(+), 1436 deletions(-) delete mode 100644 doctypes/dtd/subjectScheme/classifyDomain.ent delete mode 100644 doctypes/dtd/subjectScheme/classifyDomain.mod delete mode 100644 doctypes/rng/subjectScheme/classifyDomain.rng delete mode 100644 specification/langRef/base/subjectCell.dita delete mode 100644 specification/langRef/base/subjectref.dita delete mode 100644 specification/langRef/base/topicCell.dita delete mode 100644 specification/langRef/base/topicSubjectHeader.dita delete mode 100644 specification/langRef/base/topicSubjectRow.dita delete mode 100644 specification/langRef/base/topicSubjectTable.dita delete mode 100644 specification/langRef/base/topicapply.dita delete mode 100644 specification/langRef/base/topicsubject.dita delete mode 100644 specification/langRef/classification-domain-elements.ditamap delete mode 100644 specification/langRef/key-definitions-classification-domain-elements.ditamap diff --git a/doctypes/dtd/subjectScheme/catalog.xml b/doctypes/dtd/subjectScheme/catalog.xml index ca395c77..1bac7f66 100644 --- a/doctypes/dtd/subjectScheme/catalog.xml +++ b/doctypes/dtd/subjectScheme/catalog.xml @@ -1,15 +1,7 @@ - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/doctypes/dtd/subjectScheme/classifyDomain.mod b/doctypes/dtd/subjectScheme/classifyDomain.mod deleted file mode 100644 index 9ca35e15..00000000 --- a/doctypes/dtd/subjectScheme/classifyDomain.mod +++ /dev/null @@ -1,305 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/doctypes/rng/subjectScheme/catalog.xml b/doctypes/rng/subjectScheme/catalog.xml index 57ece5c4..f65ee3f3 100644 --- a/doctypes/rng/subjectScheme/catalog.xml +++ b/doctypes/rng/subjectScheme/catalog.xml @@ -1,12 +1,8 @@ - + - - - - - - - - DITA Subject Classification Domain - -============================================================= - HEADER -============================================================= - MODULE: DITA Subject Classification Domain - VERSION: 2.0 - DATE: [[[Release date]]] - PURPOSE: Define elements and specialization attributes - for Map Subject Classification Domain - -============================================================= - -============================================================= - PUBLIC DOCUMENT TYPE DEFINITION - TYPICAL INVOCATION - - Refer to this file by the following public identifier or an - appropriate system identifier -PUBLIC "-//OASIS//ELEMENTS DITA 2.0 Subject Classification Domain//EN" - Delivered as file "classifyDomain.mod" - -============================================================= - - (C) Copyright OASIS Open 2008, 2009. - (C) Copyright IBM Corporation 2005, 2007. - All Rights Reserved. - - UPDATES: - 2008.02.13 RDA: Created file based upon prototype from IBM - 2010.01.21 RDA: Update subjectCell content to remove - duplicate element inclusion - 2018.04.09 KJE: Removed @navtitle -============================================================= - - - elementdomain - classify-d - - -//OASIS//ELEMENTS DITA Subject Classification Domain//EN - -//OASIS//ENTITIES DITA Subject Classification Domain//EN - urn:pubid:oasis:tc:tc:dita:spec:classification:rng:classifyDomain.rng - - - -
DOMAIN EXTENSION PATTERNS - - - - - - - - - - - - - - - - - -
-
- ELEMENT TYPE NAME PATTERNS - - - - - - - - - - - - - - - - -
-
- ELEMENT TYPE DECLARATIONS - -
- LONG NAME: Topic Subject - SKOS equivalent: primary if href or keyref are specified - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - normal - resource-only - -dita-use-conref-target - - - - - - - external - local - peer - -dita-use-conref-target - - - - - - - - - - no - yes - -dita-use-conref-target - - - - - - - - - - - - - - - - - -
-
- LONG NAME: Topic Apply - - - - - - - - - - - - - - - - - - - - - - - - - - choice - family - sequence - unordered - -dita-use-conref-target - - - - - - - - - - - - - normal - resource-only - -dita-use-conref-target - - - - - - - external - local - peer - -dita-use-conref-target - - - - - - - - - - none - normal - sourceonly - targetonly - -dita-use-conref-target - - - - - - - no - yes - -dita-use-conref-target - - - - - - - - - - - - - - - - - LONG NAME: Subject Reference - - - - - - - - - - - - - - - - - - - - - - choice - family - sequence - unordered - -dita-use-conref-target - - - - - - - - - - - - - normal - resource-only - -dita-use-conref-target - - - - - - - external - local - peer - -dita-use-conref-target - - - - - - - - - - none - normal - sourceonly - targetonly - -dita-use-conref-target - - - - - - - no - yes - -dita-use-conref-target - - - - - - - - - - - - - - - - - -
-
- LONG NAME: Topic Subject Relationship Table - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- LONG NAME: Topic Subject Table Header - - - - - - - - - - - - - - - - - - - - -
-
- LONG NAME: Topic Subject Table Row - - - - - - - - - - - - - - - - - - - - -
-
- LONG NAME: Topic Subject Table Cell - - - - - - - - - - - - - - - - - - - - - - - -
-
- LONG NAME: Topic Subject Cell - - - - - - - - - - - - - - - - - - - - - - - -
-
-
- SPECIALIZATION ATTRIBUTE DECLARATIONS - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- diff --git a/specification/base-relationship-tables.ditamap b/specification/base-relationship-tables.ditamap index cfb92193..884a2b52 100644 --- a/specification/base-relationship-tables.ditamap +++ b/specification/base-relationship-tables.ditamap @@ -180,7 +180,6 @@ - diff --git a/specification/common/conref-examples.dita b/specification/common/conref-examples.dita index cd4a0f8d..ae915121 100644 --- a/specification/common/conref-examples.dita +++ b/specification/common/conref-examples.dita @@ -77,27 +77,5 @@ the ditavalref element.

yes, so that the subject scheme map can be rendered and displayed for viewing.

- - Example -

In the following example, the map is classified as covering the Linux subject, and - developing-web-applications.dita is classified as covering the Web - and development subjects. These subjects (and their keys) are defined externally in a - subject scheme map; in order to reference the subject directly without the subject scheme - map, the href attribute would be used in place of - keyref.

- <map> - <title>Working with Linux</title> - <topicsubject keyref="linux"/> - <!-- ... --> - <topicref href="developing-web-applications.dita"> - <topicsubject> - <subjectref keyref="web"/> - <subjectref keyref="development"/> - </topicsubject> - <!-- ... --> - </topicref> - <!-- ... --> -</map> - diff --git a/specification/langRef/base/subjectCell.dita b/specification/langRef/base/subjectCell.dita deleted file mode 100644 index bcd7184b..00000000 --- a/specification/langRef/base/subjectCell.dita +++ /dev/null @@ -1,37 +0,0 @@ - - - -<xmlelement>subjectCell</xmlelement> -The subjectCell element contains subjects that are associated - with topics in the first column of the row in the - topicSubjectTable. The subjects themselves have no defined - relationship across columns, other than the fact that they apply to the same - content. - - - classification - domainsubjectCell - - -
- Specialization hierarchy -

The subjectCell element is specialized from - relcell. It is defined in the classification-domain - module.

-
-
- Attributes -

The following attributes are available on this element: and , type, scope, and format.

-
- - Example -

See

- - - diff --git a/specification/langRef/base/subjectref.dita b/specification/langRef/base/subjectref.dita deleted file mode 100644 index b0002eaf..00000000 --- a/specification/langRef/base/subjectref.dita +++ /dev/null @@ -1,44 +0,0 @@ - - - -<xmlelement>subjectref</xmlelement> -The subjectref element identifies a subject with which to - classify the content. - - - classification - domainsubjectref - subject reference - - -
- Specialization hierarchy -

The subjectref element is specialized from - topicref. It is defined in the classification-domain module.

-
-
- Attributes -

The following attributes are available on this element: , , impose-role, - keyref, - keys, collection-type, linking, processing-role and toc.

-

For this element:

    -
  • The impose-role attribute has a fixed value of - keeptarget.
    • -
  • The processing-role attribute has a default value of - resource-only.
    • -
  • The toc attribute has a default value of no.
    • -

-
- - - - diff --git a/specification/langRef/base/topicCell.dita b/specification/langRef/base/topicCell.dita deleted file mode 100644 index abc251f0..00000000 --- a/specification/langRef/base/topicCell.dita +++ /dev/null @@ -1,37 +0,0 @@ - - - -<xmlelement>topicCell</xmlelement> -The topicCell element contains topics that are associated with - subjects in each following column of the row in the - topicSubjectTable. - - - - classification - domaintopicCell - - - - -
- Specialization hierarchy -

The topicCell element is specialized from - relcell. It is defined in the classification-domain - module.

-
-
- Attributes -

The following attributes are available on this element: , , type, scope, and format.

-
- - Example -

See

- - - diff --git a/specification/langRef/base/topicSubjectHeader.dita b/specification/langRef/base/topicSubjectHeader.dita deleted file mode 100644 index 82dfb50d..00000000 --- a/specification/langRef/base/topicSubjectHeader.dita +++ /dev/null @@ -1,44 +0,0 @@ - - - -<xmlelement>topicSubjectHeader</xmlelement> -The topicSubjectHeader element represents a header row in the - topic subject table. - - - - classification - domaintopicSubjectHeader - topic subject table - - - - -
- Usage information -

Use the topicSubjectHeader element to supply a header row - for a topic subject table when you want to classify topics with subjects from - different categories, a practice also known as facet classification. Each cell in the - header row identifies the subject for a different category. As a best practice, the - subjects in the same column within the classification rows must appear in the - category in the subject scheme. For instance, if the cell within the header row - specifies the Operating System category, the subjects in the column must be kinds of - operating systems.

-
-
- Specialization hierarchy -

The topicSubjectHeader element is specialized from - relrow. It is defined in the classification-domain - module.

-
-
- Attributes -

-

- - Example -

See .

- - - diff --git a/specification/langRef/base/topicSubjectRow.dita b/specification/langRef/base/topicSubjectRow.dita deleted file mode 100644 index 7ce437b3..00000000 --- a/specification/langRef/base/topicSubjectRow.dita +++ /dev/null @@ -1,32 +0,0 @@ - - - -<xmlelement>topicSubjectRow</xmlelement> -The topicSubjectRow element represents a single row of a topic - subject table. It contains topic references in the first column and subject references in - each following column. - - - - classification - domaintopicSubjectRow - - - - -
- Specialization hierarchy -

The topicSubjectRow element is specialized from - relrow. It is defined in the classification-domain - module.

-
-
- Attributes -

-

- - Example -

See .

- - - diff --git a/specification/langRef/base/topicSubjectTable.dita b/specification/langRef/base/topicSubjectTable.dita deleted file mode 100644 index f19105f5..00000000 --- a/specification/langRef/base/topicSubjectTable.dita +++ /dev/null @@ -1,181 +0,0 @@ - - - - -<xmlelement>topicSubjectTable</xmlelement> -The topicSubjectTable element represents a specialized - relationship table that associates topics with subjects. Search tools might use these - classifications to retrieve content that is relative to a specific subject or combination of - subjects. - - - - classification - domaintopicSubjectTable - - - - -
- Usage information -

In a topicSubjectTable, the first column is reserved for - references to content. Subsequent columns are reserved for subjects that classify the - content; each column supplies the subjects for the category that is identified in the - header. The table resembles a traditional relationship table in which the first column - identifies the source and the other columns identify the targets, but the relationship - reflects the subjects covered by the content rather than linking between documents.

-

In a reltable, topics in any given column establish relationships - with topics in every other cell of the same row. In a - topicSubjectTable, topics in the first column are related to all - of the subjects in the row, but no relationship is implied between subjects in different - columns of the same row.

-
-
- Specialization hierarchy -

The topicSubjectTable element is specialized from - reltable. It is defined in the classification-domain module.

-
-
- Attributes -
-
- - Example -

The topic subject table below associates topics with goals for retrieval and with operating - systems for filtering. The subjects are defined in a separate subject scheme map.

- - Subject scheme map -

- This example uses hasKind - elements, which were removed from 2.0 at today's TC meeting. Leaving them here now - rather than editing the example, with the expectation that this element will also be - removed as part of a proposal to remove the classification domain. If that domain is - retained, we need to update this example. -

- <subjectScheme> - <hasKind> - <subjectdef href="goalType.dita" keys="goal"> - <subjectdef href="performanceGoal.dita" keys="performance"/> - <subjectdef href="reliabilityGoal.dita" keys="reliability"/> - </subjectdef> - <subjectdef href="operatingSystem.dita" keys="os"> - <subjectdef href="linuxOS.dita" keys="linux"/> - <subjectdef href="unixOS.dita" keys="unix"/> - <subjectdef href="windowsOS.dita" keys="windows"/> - </subjectdef> - </hasKind> -</subjectScheme> - - - Topic subject table -

The following topicSubjectTable classifies several topics - according to subjects defined in the previous map. As with any - topicSubjectTable, the first column is used to specify topics. - In this specific example, the second column is used to specify a goal, based on the "goal" - subject in the header. The third column is used to specify an operating system. Based on - those definitions, the following classifications are made by this table:

-
    -
  • The topics - configure-cron-for-efficiency.dita and - allocating-raw-storage.dita are each - classified by the goal of performance; they - are also classified by the operating systems - linux and unix.
    • -
  • The topics analyze-web-logs.dita and - detect-denial-of-service-attacks.dita - are each classified by the goal of "reliability"; they are also - classified by the operating systems linux, - unix, and windows.
    • -
  • No relationship is defined between subjects in the table, meaning that this table does - not define any relationship between the goal of performance and the - operating systems linux or unix.
    • -
- <map> -<!-- ... --> -<topicSubjectTable> - <topicSubjectHeader> - <topicCell type="task"/> - <subjectCell> - <topicsubject keyref="goal"/> - </subjectCell> - <subjectCell> - <topicapply keyref="os"/> - </subjectCell> - </topicSubjectHeader> - <topicSubjectRow> - <topicCell> - <topicref href="configure-cron-for-efficiency.dita"/> - <topicref href="allocating-raw-storage.dita"/> - </topicCell> - <subjectCell> - <topicsubject keyref="performance"/> - </subjectCell> - <subjectCell> - <topicapply keyref="linux"/> - <topicapply keyref="unix"/> - </subjectCell> - </topicSubjectRow> - <topicSubjectRow> - <topicCell> - <topicref href="analyze-web-logs.dita"/> - <topicref href="detect-denial-of-service-attacks.dita"/> - </topicCell> - <subjectCell> - <topicsubject keyref="reliability"/> - </subjectCell> - <subjectCell> - <topicapply keyref="linux"/> - <topicapply keyref="unix"/> - <topicapply keyref="windows"/> - </subjectCell> - </topicSubjectRow> - <!-- ... --> -</topicSubjectTable> -</map> -

A table view of this topicSubjectTable might look as follows. - This is only one of many possible views; to aid in understanding the example, the content - topics in the first column are displayed using only their file names, and related subjects - are displayed using only their keyref attribute value.

- - - Task - Goal - Operating system - - - - configure-cron-for-efficiency.dita - -allocating-raw-storage.dita - - - performance - - - linux -unix - - - - - analyze-web-logs.dita - - -detect-denial-of-service-attacks.dita - - - reliability - - - linux -unix -windows - - - - - - - - diff --git a/specification/langRef/base/topicapply.dita b/specification/langRef/base/topicapply.dita deleted file mode 100644 index dbfce6e7..00000000 --- a/specification/langRef/base/topicapply.dita +++ /dev/null @@ -1,55 +0,0 @@ - - - -<xmlelement>topicapply</xmlelement> -The topicapply element identifies subjects that qualify the -content for filtering or flagging but not retrieval. The topicapply element -can identify a single subject. Additional subjects can be specified by nested -subjectref elements. - - - - classification - domaintopicapply - - - - -
- Specialization hierarchy -

The topicapply element is specialized from - topicref. It is defined in the classification-domain module.

-
-
- Attributes -

The following attributes are available on this element: , , impose-role, keyref, keys, collection-type, - linking, processing-role - and toc.

-

For this element:

    -
  • The impose-role attribute has a fixed value of - keeptarget.
    • -
  • The processing-role attribute has a default value of - resource-only.
    • -
  • The toc attribute has a default value of no.
    • -

-
-Example

The map content should be retrieved for Apache Tomcat and hidden as irrelevant for operating - systems other than Red Hat or SUSE.

<map> - <title>Installing Apache Tomcat on RedHat or SuSE Linux</title> - <topicsubject href="../controlledValues/tomcatServer.dita"/> - <topicapply> - <subjectref href="../controlledValues/redhatLinux.dita"/> - <subjectref href="../controlledValues/suseLinux.dita"/> - </topicapply> - <!-- ... --> -</map> - - diff --git a/specification/langRef/base/topicsubject.dita b/specification/langRef/base/topicsubject.dita deleted file mode 100644 index 0d8705b4..00000000 --- a/specification/langRef/base/topicsubject.dita +++ /dev/null @@ -1,51 +0,0 @@ - - - - -<xmlelement>topicsubject</xmlelement> -The topicsubject element identifies the subjects that are - covered by a topic or map. - - - - classification - domaintopicsubject - topic subject - - - - -
- Usage information -

To identify a primary subject, refer to the subject with the - topicsubject element itself. Secondary subjects can be specified - by nested subjectref elements.

-
-
- Specialization hierarchy -

The topicsubject element is specialized from - topicref. It is defined in the classification-domain module.

-
-
- Attributes -

The following attributes are available on this element: , , impose-role, keyref, keys, processing-role - and toc.

-

For this element:

    -
  • The impose-role attribute has a fixed value of - keeptarget.
    • -
  • The processing-role attribute has a default value of - resource-only.
    • -
  • The toc attribute has a default value of no.
    • -

-
- - - - diff --git a/specification/langRef/classification-domain-elements.ditamap b/specification/langRef/classification-domain-elements.ditamap deleted file mode 100644 index 69d95fb5..00000000 --- a/specification/langRef/classification-domain-elements.ditamap +++ /dev/null @@ -1,15 +0,0 @@ - - - - Classification domain elements - - - - - - - - - - - diff --git a/specification/langRef/key-definitions-base-elements.ditamap b/specification/langRef/key-definitions-base-elements.ditamap index b0761990..e95a70ae 100644 --- a/specification/langRef/key-definitions-base-elements.ditamap +++ b/specification/langRef/key-definitions-base-elements.ditamap @@ -20,7 +20,6 @@ - diff --git a/specification/langRef/key-definitions-classification-domain-elements.ditamap b/specification/langRef/key-definitions-classification-domain-elements.ditamap deleted file mode 100644 index 112d6807..00000000 --- a/specification/langRef/key-definitions-classification-domain-elements.ditamap +++ /dev/null @@ -1,13 +0,0 @@ - - - - Keys for classification domain elements - - - - - - - - - diff --git a/specification/langRef/quick-reference/base-elements-a-to-z.dita b/specification/langRef/quick-reference/base-elements-a-to-z.dita index 7205897e..72e8f96b 100644 --- a/specification/langRef/quick-reference/base-elements-a-to-z.dita +++ b/specification/langRef/quick-reference/base-elements-a-to-z.dita @@ -138,12 +138,10 @@ - - @@ -155,13 +153,10 @@ - - -