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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: Re: [xliff] csprod01 comment 001, improved Format Style Module Processing Requirements

Hi Bryan,

I do not think that we actually have to prescribe a validation method. I just think that we should give a normative guidance how to create a working snippet and obviously we should not reinvent the wheel here..

I see that the browser criterion is probably the most practical, still we should not give such a sloppy criterion in a normative PR.
I think a note nearby could say that.

I was doing some research looking for a suitable normtaive W3C reference that we could use.
i believe we should say something along the lines that parsing of the snippet following this fragment parsing algorithm 
should produce a valid DOM tree

So there is ultimately a DOMCORE normative refernce but the handling is given by the HTML5 candidate recommendation.

IMHO, if the snippet is parsed as advised above, the result even should validate..

I hope this helps

Dr. David Filip
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
mailto: david.filip@ul.ie

On Mon, Jul 1, 2013 at 9:17 PM, Schnabel, Bryan S <bryan.s.schnabel@tektronix.com> wrote:

Hi All,


Regarding comment 001, Format Style Module Processing Requirements, I see in the Actions (to be) Taken cell it says “Bryan to add the PR with reference to HTML standard object model.”


I remember we discussed this, but my memory is that we could not determine an appropriate “standard object model.”


And I’m still at a loss to solve this.


If we are talking about the HTML DOM, I think that’s very much overkill. And as we said before, and XML validation against an HTML DTD is also overkill. Even the very handy W3C HTML validator (http://validator.w3.org/ ) fails HTML blurbs that really should pass. For example, if the Format Style Module markup resulted in the following just-in-time HTML snip, it would render nicely in a standard HTML browser (but fail in the validator):








In fact the language in the initial comment was:


“new Processing Requirement: The fs and subFs MUST be configured in such a way that the resulting HTML snippet is valid, such that it can be rendered by a standard HTML browser”


Please let me know if you have advice on what HTML standard object model I should refer to. Or, let me know if you think the language from the initial comment will suffice.






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