RE: Re: [ACTION-160] (related to [ACTION-135] too) Summarize specialRequirements

Hi Felix,

In the case of forbiddenChars I think the matter of which regex syntax to use can be solved by either: 

a) Selecting a single syntax (maybe the one of XSD like Shaun noted). But I think the data will be validated outside of XML most of the time, using XSD’s may not be a good idea.

b) Having an extra attribute to specify which syntax is used (like Giuseppe did in his latest proposal)

c) Defining the sub-set of regex expressions that can be used, and make sure it’s compatible across most regex engines. That’s I think the simplest and more interoperable solution. The drawback is that someone has to take the time to define that list once.


> I understand your argument about what currently you 
> do the checking later in the chain. But what about 
> doing the checking earlier, with schematron, and then 
> just passing the results to the application(s)?

That make little sense to me: that type of checks is best done interactively, or at some point when the translation can be fixed without having consequences in the process, so either when translating, or just after. But not when the document is back in its original format.

I have nothing against Schematron, but if the original data is a database and the tool used by the translator doesn't know anything about XML, why force using an XML for this? Sure XML is involved in the process, but just as an intermediary.


> Another benefit is that you can get content creators 
> at least from the XML realm to provide and use 
> these schematron files.

For me, I'd rather have them spent time making sure the constraints are set and can be passed to the translation process in a standardized way, so the checks can be done where it's best and by whatever tool the process owner deems the best.

Besides, even when using Schematron, having a single parameterized script that use the ITS data as input would be better than hard-coding the checks in the script. Write once and re-use it forever.

Cheers,
-yves

Received on Tuesday, 10 July 2012 13:59:39 UTC