RE: [all] Call for consensus on specialRequirements

Hi Micha, all,

> 3) What kind of pointer do you mean?

An attribute that would allow to map the ITS data category to a non-ITS-native implementation.

We have such thing for several data categories like locNote (the locNotePointer that points to the construct of a non-ITS vocabulary that offers the same functionality).

This section: talks about this a bit more (adding vs pointing)

At some point the group probably needs to decide in which of the new data categories it make sense to have those pointers.

Not something urgent to solve.

4) Agreed. I have to confess that I just copy&pasted the text without thinking too much about it. Thanks for pointing this out.


Dr. Michael Kruppa, Senior IT-Consultant
Tel.: +49 69 972 69 189 Fax: +49 69 972 69 204; E-Mail: Cocomore AG, Gutleutstraße 30, D-60329 Frankfurt
Internet: Facebook: Google+: Cocomore ist aktives Mitglied im World Wide Web Consortium (W3C) und im Bundesverband Digitale Wirtschaft (BVDW) Cocomore is active member of the World Wide Web Consortium (W3C)
Vorstand: Dr. Hans-Ulrich von Freyberg (Vors.), Dr. Jens Fricke, Marc Kutschera, Vors. des Aufsichtsrates: Martin Velasco, Sitz: Frankfurt/Main, Amtsgericht Frankfurt am Main, HRB 51114

dmexco 2012 in Köln: Besuchen Sie unseren Messestand auf der internationalen Leitmesse für die Digitale Wirtschaft am 12. und 13. September 2012. Sie finden uns in Halle 7, Stand E057.
dmexco 2012 in Cologne: Come to see us on September 12 and 13 at the Digital Marketing Exposition and Conference (hall 7, stand E057).

-----Ursprüngliche Nachricht-----
Von: Yves Savourel []
Gesendet: Montag, 30. Juli 2012 14:48
An: Michael Kruppa;
Betreff: RE: [all] Call for consensus on specialRequirements

Hi Michael, all,

Thanks for the text and examples, and to help this to move forward.

I have a few notes so far:

1) Two vs. One 

Those two constraints could probably be split into two data categories. Besides being constrains they have little in common. Having them separated may also help in implementation: some tools may implement only one rather than none.

2) List for forbidden Characters

Instead of the very basic list of Unicode code points, I think we could go the extra length and use a very simple regex based on Arle's proposal here:
But maybe limiting it to the [] ^ - (and \uHHHH) functions. The notation would also make [] optional so even forbiddenChars="abc" would be fine (= "[abc]"

- Those are supported as far as I can tell by all regex engine without mapping.
- they would make ranges a lot easier to declare.

3) Do we want pointers in the global rule?

This would add the capability to map non-native-ITS constructs to be mapped to the data category/ies (as long as the values are the same).

4) Scope (a general remark, not just for this data category)

The text says: "The information applies to the textual content of the element, including child elements, but excluding attributes."

Why do we say (here and in many other places) "the information applies to the textual content of the element"? If the selector points to an attribute node (that could be translatable), then the information applies to the value of the attribute not to any textual content of the element.

Would there be a better way to word this text? Something like:

When the selection is an element node the information applies to the textual content of the element, including child elements, but excluding attributes. When the selection is an attribute node, the information applies to the value of the selected attribute.


Received on Tuesday, 31 July 2012 08:21:00 UTC