merging of parts
Bob Jolliffe
In the first step towards merging of parts I have converted your part
2 from its original doc format to a simple xhtml which shares a common
stylesheet with the part 1 stuff. I suggest we stick with this until
we are done combining all the sections. Apart from the fact that it
is useful to have a clean web based version it will be much easier to
generate a clean docx, odf and/or pdf version off the xhtml than
trying to remain consistent with word. Besides which it is also much
easier now to place under version control. Removing all the pesky
extra tags that word processors are wont to introduce kept me up till
the early hours of this morning so I hope you are happy to work on the
xhtml version for now (docbook would in fact have been better but at
least everyone is familiar with html and there are decent editing
tools so it should be relatively painless). There is some work which
needs to be done in terms of defining section levels and generating a
TOC but we'll worry about that in a bit.
It would be good if you can reorganise the conceptscheme section to
reflect the agreed splitting of concepts.
I've also done some fairly major hacking of content (Don't panic - we
still have the original content). Basically I have restricted the
content to the scope of part 2 which describes the common codelists,
concepts and hierarchies. By far the most important part of this
section is the authoritative permanent url to the data dictionary. We
might consider producing a pdf annexe of the data dictionary content
(i) when it is complete and (ii) if it isn't too enormous. Depending
solely on an authoritative URL might be a bit fragile.
Rules for the production and use of the custom codelist and hierarchy
structures have to be incorporated into part 1, which is what I am now
returning to.
The pretty pictures can be used as part of the implementation
guide/tutorial material.
There is still quite a lot of document organisation to be done, but
anyone who is interested can follow along by checking out the current
stuff (svn co http://svn.sdmx-hd.org/sdmxhd/schematron-sdmx-hd) or
browsing through
http://sdmx-hd.org/repositories/browse/sdmx-hd-standards/schematron-sdmx-hd,
which is better than sending word files around by email.
I'm getting back to part 1 now. Will try and incorporate all the
rules chopped out from part 2 though there are some we have to
discuss.
Regards
Bob
Gary Patchen
DONE
gary patchen
lead consultant
direct + 41.(0)58.307.7094
mobile +41.(0)79.333.1339
gary.p...@b-i.com
www.b-i.com
blue-infinity headquarters
t +41(0)58.307.7000
f +41(0)58.307.7001
INTERNATIONAL
t +800.307.70.000
f +800.307.70.001
b-i branding.technology.integration.
The information in this e-mail, and those ensuing, is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please destroy this message and notify us immediately.
Please think of the environment before printing this email