Milestones

[Patrick Durusau <patrick@durusau.net>]

Eric and Friends,

Since I won't be on for the milestone conversation, some comments about 
the current wiki page that will become our draft standard. I will just 
list the headers of each section.

Maybe helpful to look at the OASIS TC Handbook, under Technical 
Committee Specifications,

Download one of the templates under Specification Templates.

Note that we have to have normative and non-normative references in the 
first section.

Any conformance clauses are going to have to occur before any annexes.

With that, on the content in the wiki:

1) Introduction - 1.0, 2.0, 3.0, 4.0 into a single introduction. Need to 
be short but powerful.

2) Terminology and references

I am concerned about section 5 - concomitant representation of ICOM in 
UML and RDF.

Mostly because we find that RDF cannot represent all the aspects of ICOM 
as specified in UML.

Actually I don't think having two representations of any standard is a 
good idea.

Too much chance that the representations would get out of synch.

Can always have a non-normative mapping as an annex but it would be a 
non-normative mapping.

3) 6. The ICOM High-Level Concepts

Remember that we need to specify a *normative* model. That is one that 
will support conformance requirements.

In order to have interoperability, there are going to need to be some 
hard and fast rules that everyone obeys.

Speaking of which, ;-), are we going to express the ICOM objects in 
prose with *all* their properties?

Essentially duplicate the figure 4?

So which is normative? The prose or the UML?

I am a text person so I really prefer the prose but that is just me.

Plus all the rest of section 6 would have to be written as normative text.

7.0 Use Cases for High-Level Core Concepts for ICOM - This should be a 
non-normative annex.

8.0 Containers in Space - shouldn't this be with the normative text in 6?

9.0 Some parts of this are normative, Yes?

9.0 - Mapping between UML Model and RDF model of Metadata - move to 
non-normative annex.

What else in 9.0 is normative?

10. Use Cases for Category and Bond. - Move to annex for sure.

11.0 Artifact Modules - need to move up to normative text

12.0 Subjects: Group, Role, Actor - move up to normative text

13.0 - Would make a good separate page at wiki but probably not part of 
the standard.

Hope you and the rest of the gang are having a great day!

Patrick

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau