[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 24 hours to comment
[[[]]]
- Bottom line. Internationalized links are supported in (draft) WebCGM 2.0, and were supported in (Rec) WebCGM 1.0 as well. Unicode (UTF-8 or UTF-16) may occur in object id's, object names, and in link fragments. [LH: as well as link base addresses, I think].
- Confusing requirements. There has been confusion between the two paragraphs of section 2.5 in the WebCGM 2.0 Requirements Document [1]. It has two causes: difference between the general requirements for (scalable) Web graphics formats and specific application constituency requirements; and some previous misunderstanding of the implications of IRI and internationalized links.
- [1] http://www.cgmopen.org/technical/WebCGM_20_Requirements.html
- Explanation. The requirements in the two paragraphs of 2.5 come from two different sources. Firstly (1st pgph of 2.5), there is a set of general requirements for a scalable vector graphics format, drafted by the W3C Graphics Activity about 10 years ago [2]. In the case of Unicode support in the WebCGM components involved in object linking, these were adopted into WebCGM 1.0, and in fact are further clarified in (draft) 2.0. (And indeed are implemented already.)
- [2] http://www.w3.org/Graphics/ScalableReq ,
- Secondly (2nd pgph of 2.5), there are more recent requirements statements that arise from the major WebCGM constituencies in aerospace that are applying WebCGM (via Cascading Profiles). In these constituencies, there is no present need for internationalized links. There is concern for the timely publication of WebCGM 2.0, and a general concern that WebCGM 2.0 should not bog down in sorting out of all fine details of internationalized links.
- Conclusion. The internationalized link support currently in draft WebCGM 2.0 (which is a clarification of the 1.0 capabilities) meets the generalized requirements articulated for Web graphics formats [2], and provides a foundation from which specific application requirements can work. Specific application constituencies can add whatever further restrictions might be appropriate, via Cascading Profiles.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]