Project

General

Profile

Bug #151

need doctype equivalence specification

Added by Matt Jones over 19 years ago. Updated over 15 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
metacat
Target version:
Start date:
09/22/2000
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
151

Description

Metadata document types will certainly evolve, and as they do, some applications
that depend on those types will break. Others will still function fine, because
the changes to the doctype will be inconsequential for that application. We
need a mechanism for indicating the "relationships" between metadata document
types, and possible a mechanism for flagging certain document types as
"suitable" for a particular application (meaning the application knows the
structure of the doctype well enough to utilize the metadata content. This is
closely related to bug #144 that is working on. It is
also closely related to the HyTime "Architectural Forms" specification in the
SGML world.

History

#1 Updated by Matt Jones almost 19 years ago

Changed milestone for several bugs. Some of these we should consider marking
INVALID or WONTFIX.

#2 Updated by Matt Jones over 18 years ago

Moved issues that we do not intend to address during the current release to the
'Postpone' milestone.

#3 Updated by Matt Jones over 15 years ago

This is being addressed within the context of SEEK SMS and will not be addressed
directly in Metacat. Marking WONTFIX.

#4 Updated by Redmine Admin about 7 years ago

Original Bugzilla ID was 151

Also available in: Atom PDF