OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-collab message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: MS Change tracking Question


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings!

More a question for Darrin but I wanted to capture it to the collab
list as well.

Reading part 1 of OOXML/ISO 29500, section 17.7.4.15 and it reads in par
t:

*****
This element specifies a unique four digit number which shall be used
to determine the editing session in which this style definition was
last modified.
*****

The "val (Long Hexadecimal Number Value)" attribute of that element,
immediately following reads in part:

*****
Specifies a number value specified as a four digit hexadecimal
number), whose contents of this decimal number are interpreted based
on the context of the parent XML element.

[Example: Consider the following value for an attribute of simple type
ST_LongHexNumber: 00BE2C6C.

This value is permitted, as it contains four hexadecimal digits, each
an encoding of an octet of the actual decimal number value. It can
therefore be interpreted as desired in the context of the parent XML
element, end example]

The possible values for this attribute are defined by the
ST_LongHexNumber simple type (§17.18.50).
*****

And 17.18.50 reads in part:

*****
ST_LongHexNumber (Eight Digit Hexadecimal Value)

This simple type specifies a number value specified as a four octet
(eight digit) hexadecimal number, whose contents are interpreted based
on the context of the parent XML element.

...

This simple type's contents have a length of exactly 8 hexadecimal
digit(s).
*****

Do you see the shift from "four digit hexadecimal number" in 17.7.4.15
(twice) and elsewhere, to "exactly 8 hexadecimal digit(s)" in the
reference definition in 17.18.50?

I am assuming that what was meant was:

"unique four digit number" = four digit decimal number (no more, no
less), unique to the document instance, but expressed as a hexadecimal
number (always).

Yes?

I think that is a fair reading and probably how it is implemented but
the language about "digits" is ambiguous.

I haven't gotten as far as I would like but have done some "lite"
reading of parts of the change tracking sections. ;-)

Hope you are having a great week!

Patrick


- -- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor 13250-5 (Topic Maps)

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJWulQvAAoJEFPGsgi3Mgycsr8QALO3Lgn7oGqrWxhhon57Meol
i6O+xxONZFAdqCmB4lvdVlcGj8GeVC4FRvJwoVPu6XngftmySavnJpqa/6fwgxCN
7HcYw9bPPNMlLEewvV+38HWzBOQdh4f/IjxoCyQW/QJ8uSz3unCFRj+MhI3Z4/5W
Q2oPPRYVrsWc4Yv/6BeuIzZhDPO/crXqZmI2YVKThyJfRHzBN4M6LdSGdU+QtBl6
JjPU137yOfG7uCqPlKevwHrFunKkWZYQhdpzeFcr8Ci0is25GRUgc8jyUt21RW68
nyJq2t8pEAb4Vu/4zzk4lExV1PSumoZu8/UtfYaXO7rA1wW8QBGrqI4TsahkLkst
sbGxFu8W/FT30QDORTimrgsqx15mM4ITZ5PYm1kQQfIWnAKryLhb7u5i3wMVM28z
tgZq4avTrZJ+u6yd7rKJap9DCVSDCu86LxioBW4b6srv5WC1/0dW0thLOpq4zOgC
RfVjnmh63gRBDyXeOrsr4Kf6Zkouh8ZC1+hEktYhV7FM7rMqoDo7Hkn35adIWf6y
RzH/F9sKm1ojd9MIfIAcn9RDY6d+DyHHS4nikkr4XoWj9QpKSZAibdvBUouxKNYq
n/efLbWEMUMDQC7R46OFvKs05GKRuXHY5AfII0cN0PMPYr3/w+RYafqPhaGhyCAt
VrXwi8EIxf9buDMOKcru
=/F3u
-----END PGP SIGNATURE-----


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]