[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Question about default for @format when linking to file.htm
I don't personally feel confident that there are NO valid reasons to use format="htm". For example - since there was no previous prohibition on using "htm" - companies today could have used explicit values of format="htm" in their maps, potentially with special processing based on that value. This would make sense if they use ".htm" as the extension for all html files anyway. For that reason, I think I would lean towards SHOULD.
Keep in mind the RFC-2119 meanings of the normative terms:
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
+1 919 682-2290; kriseberlein (skype)
On 3/17/2014 7:56 AM, Bob Thomas wrote:
I prefer "must", but I don't feel strongly about it.
On Mon, Mar 17, 2014 at 5:33 AM, Chris Nitchie <firstname.lastname@example.org> wrote:
On Mar 13, 2014, at 6:24 PM, "Robert D Anderson" <email@example.com> wrote:
I see a draft comment in the write up for proposal 13107 (assume a default value for @format based on the extension of the linked resource. Bob's comment states:
This description needs to specify that a ".htm" extension MUST imply format value "html".
That's a slight change from the approved proposal, so I wanted to send to the TC before making that change.
1. Is that correct - an extension of "htm" means format="html" (rather than format="htm")?
2. Is this something that we want to list as MUST with a reference to the RFC terminology?
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit (http://dita-ot.sourceforge.net/)
+1 720 201 8260
Instant messaging: Gmail chat (firstname.lastname@example.org) or Skype
Time zone: Mountain (GMT-7)
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php