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


Help: OASIS Mailing Lists Help | MarkMail Help

saf message

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

Subject: TC Admin comments on SAF V1.0 CS01

Members of the SAF TC,

In catching up on work today, I came across a list of items that came
up when we were preparing SAF V1.0 CS01. I am providing these to you
as input for future iterations of the specification.

1. Use of someone else's domain name in examples.

We noted in the examples throughout the document use of the domain
saf.com. This domain is the property of the SAF Southern Aluminum
Finishing Company. Inc. in Atlanta, GA.

IANA has reserved example.com, example.org and similar domains for
exactly this purpose. We ask that you change the examples to use these
domains in future versions of the specification.

Our concern, aside from avoiding any possible complaints from the
domain's owner, is that the 404's resulting from links such as
http://saf.com/prescriptions/aspirin/12345 in the document could
distort results of web analytics and other automated applications.

2. In section 1.3 Normative References, line 55, the informational box
on how to format citations was left in the document. It need not be
there and you can remove it from future versions of the document.

Just so you all know, it is our policy not to touch your content. We
consider it sacrosanct and limit our work to adding the cover pages
and headers and footers necessary for publishing your work. That
bright line however is the reason we would not make such a fix and
bring it to your attention instead.

3. In section 1.2 XML Namespaces, line 41, you mention the namespace
"saf" and http://docs.oasis-open.org/saf/ns/symptoms/2011/10. However,
the CS doesn't have a schema or other computer language file formally
declaring the namespace.

When such a formal declaration is made in an accompanying computer
language file, TC Admin adds a Declared Namespaces field to the spec's
cover page and we create a namespace document as well that will be
retrieved should anyone follow the namespace URL.

If the TC does intend to create a formal declaration then, when that
is available in a future spec, we will include the information above.
However, if you are not formally declaring it, we'd ask that you
remove it from the spec to avoid any confusion.

4. In a future version, please reapply the Heading 1 style on line 406
to fix the numbering for section 2.9.

Thanks & let us know if you have any questions about any of this.

Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

TC Administration information and support is available at

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

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