[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [saf] TC Admin comments on SAF V1.0 CS01
Hi Chet, Thanks for the comments once again. We have actually spotted most of them already, but we were not sure about the process to correct, e.g. the saf domain name. Do we have to go through the whole public review cycles again, or because it's such an obvious mistake we can avoid that? Or maybe even publish an errata document? Thanks again and regards, Stavros -----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Chet Ensign Sent: 23 May 2012 16:28 To: email@example.com Subject: [saf] 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 ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open --------------------------------------------------------------------- To unsubscribe, e-mail: firstname.lastname@example.org For additional commands, e-mail: email@example.com ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.