Hi Pete, Thanks for your comments. I'll respond to a few of these if I can.
I've added a description for oslc_am:order. This was just an omission on my part. We discussed the nature of the property last time. You are absolutely correct we have not proposed any coordinate system as of yet. This needs to be done. The justification for layers comes in part from some behavior we have in Rational Software Architect which does support layers on individual diagrams, and most importantly this behavior is for the most part independent of the semantic meanings of the views participating in the layer. An RSA user can select arbitrary views in an RSA diagram and add them to a custom defined layer. These layers can be selectively hidden. The main justification for layers in general is to provide a means to help simplify overly complex and large diagrams. I should also note that AM providers are obliged to support layers. If the service provider already does so this specification just describes how it can be presented to the client for use. We have discussed a lot about the usefulness of layers with SVG. As you point out diagrams leveraging SVG have many architectural advantages. Many of these overlap with the capabilities provided for by this Diagram resource specification (i.e. hot spots and click through). In general we feel that most of what the Diagram resource provides is for raster images and diagrams, not SVG. We can not guarantee, nor can we require that diagrams only be rendered with SVG. As a result we offer this resource specification to provide that information. Thanks, jim conallen Rational Design Management (DM) Integration Architect, OSLC AM Lead [email protected] Rational Software, IBM Software Group From: "Pete Rivett" <[email protected]> To: James Conallen/Philadelphia/IBM@IBMUS, <[email protected]>, Date: 08/15/2012 09:45 PM Subject: RE: [oslc-ArchMgmt] OSLC AM General Meeting 15-August Oslc_am:order has no description. What coordinate system are you assuming for diagrams? Without a defined system Diagram Area is somewhat meaningless. Not sure the Usage Scenarios justify either of these anyway. I’m also not clear on the justification for Layers – I cannot think of any modeling tool that allows a single diagram to be layered in any way. The Usage Scenarios ignore (and mitigate against) the use of SVG – which is a common (and preferred – due to its compactness, quality and extensibility e.g. support for popups) format for diagrams from modeling tools and is natively supported by all browsers (except IE8 and earlier). Ø This should be a <img> tag with the URI of the diagram resource. Ø … Ø For HTML documents the user can simply insert a <img> tag with the src attribute set to the diagram resource URI. <img> is not always appropriate for images: see http://www.w3schools.com/svg/svg_inhtml.asp for SVG options Ø HTML has a <map> tag that allows the user to click in a specific area of an image, and the browser will navigate to that page. Again this is not appropriate for SVG which can embed external links directly Regards Pete -- Pete Rivett ([email protected]) CTO, Adaptive Inc 65 Enterprise, Aliso Viejo, CA 92656 cell: +1 949 338 3794 Follow me on Twitter @rivettp or http://twitter.com/rivettp From: [email protected] [ mailto:[email protected]] On Behalf Of James Conallen Sent: Wednesday, August 15, 2012 11:20 AM To: [email protected] Subject: [oslc-ArchMgmt] OSLC AM General Meeting 15-August If you have time please look over these two documents before tomorrows meeting. http://open-services.net/bin/view/Main/AmDiagramResource http://open-services.net/bin/view/Main/AmPredefinedQuery We will discuss these topics. Thanks, jim conallen Rational Design Management (DM) Integration Architect, OSLC AM Lead [email protected] Rational Software, IBM Software Group
