4.2.2 Service Specifications

[Patrick Durusau <patrick@durusau.net>]

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

Greetings!

After reading 4.2.2 Service Specifications (including its
subsections), I am left with the impression that it is wholly
non-normative.

There is no normative description of the syntax which I must use to
include the description of a service or any other normative
instruction as far as I can tell.

Shouldn't this be non-normative?

Perhaps an annex that gathers all the non-normative material together?

Hope everyone is having a great day!

Patrick

- -- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Former 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSKNhRAAoJEAudyeI2QFGoIxgP/jVKsGoFFZVpSybBRwSFsto1
OM5PMkicyXuZtUC/Dfpsfq+1WajuTfDfzBPWIltiVHveOJwC3z70Kia6X4e+6FAW
rLbUUUln5diz+7gMjU3x8FDX9O7EUHHo47GF9eOYO0rY3dgGqDm2buIu8SR/TKq+
GHcKrLEF+MEmj8uEcByH5/KTjzgqB1M1Inv7pZztEG5pdIcMr41ZYdYr3Shro+nz
Ramp6uCKrF8D+5D5mDpwopGMzAOUbzgONukj3kOzLM1aYHHO/PgAaGC376vpEBO/
/k6ttxIB4MI8R7+LRyTG0+NmdfQc8TUajBq/qOJ4PraCTWjJAI7Oom+90QDtoLCN
XOOeUlbJ/+Qvj618j9B0FGgeTi5ASqMvkTHPWHrX6U4AMP1rinqP0DBnidNRM7jG
KnKNBOh/1iwASZJNsk7aaI2SzXeQJ+y65Z8OOLASIy0a05vipMyzuwZZ7GpniaSw
8wxNGdlc5mhm/7kDeSH6qgKdUvurMEOfUa35WD3zIR5cZcHF/87u1xYY6gxBb5KQ
XKrW4B+DfvcCshasy6A5bnaHC36OUnWBkhdGJleched7xIpjiS8z8p0akTDodaUB
Xdjstugff8H0j9F/A5Ic5uHJy8MJTN27kUaI8o0+y6qu/gsOAFKbmr57gM3tlZLm
hq1jQ5790IPxu59/i+C+
=GwGf
-----END PGP SIGNATURE-----