[NeXus-committee] Shouldn't we distinguish class type (base|application|interface?) and status (proposed|accepted|obsolescent?|retired?) ?

[Joachim Wuttke]

Currently, our "category" mixes two distinct properties: the class type
(base, application) and the status (proposed, accepted).

The documentation is not entirely consistent; if I remember correctly,
there are places where "contributed" seems to mean "proposed
application definition", but right now the directory also contains
a proposed base class. This is confusing, and it precludes the
introduction of new class types (interfaces?) or statūs (obsolescent
and retired?).

I suggest a simple solution: split "category" into "type" and "status".

Could you please comment at
   https://github.com/nexusformat/definitions/issues/298

Does this require a vote?

- Joachim

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4916 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.nexusformat.org/pipermail/nexus-committee/attachments/20140826/ee76498f/attachment.p7s>