RE: RE: Proposal: a building block approach to XML design
Are we talking set-up and occasional change, or are we talking message by message? The first is something that I have taken to calling a Configuration Framework, and I see it as critical to scaling out the internet of things and for BIM-Based Enterprise interactions with energy and operations. In my case, I am trying to formalize the small set of legal lego's that would allow a complex system tto initially announce/negotiate the types of messages involved. The second is often based on inheritance (including cross-schema inheritance) and can be put together using tools such as CAM. On the other hand, WS-I profiles strictly forbid generic inheritance. Both are interesting spaces, toward which one are you aiming *this* conversation? tc "If something is not worth doing, it`s not worth doing well" - Peter Drucker Toby Considine TC9, Inc TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com/ blog: www.NewDaedalus.com -----Original Message----- From: Costello, Roger L. [mailto:email@example.com] Sent: Thursday, July 19, 2012 5:35 AM To: firstname.lastname@example.org Subject: RE: Proposal: a building block approach to XML design Thanks David and Michael. Good comments. Suppose I create building blocks as follows: -- I place each building block into a separate schema file. -- I assign each building block a different namespace. So I have a bunch of building blocks, each in a different namespace. Thus, requirement (1) has been met: > (1) Need to identify an appropriate set of building blocks. The Lego pattern also requires: > (2) Need to specify the rules for assembling the building blocks. NVDL  can be used for this. NVDL is great for specifying how components in different namespaces are to be assembled. Here's the strategy: the user hands to the web service an NVDL document, "Hey, here are my assembly instructions, please construct an XML document that meets these assembly instructions." But web services aren't good at this. Users can't give a web service a set of assembly instructions. Web services merely provide a menu of pre-assembled XML documents and the user can only select from the menu. So how do we empower users of web services to "get what they want" and not what the web service has already pre-assembled? /Roger  NVDL tutorial: http://www.xfront.com/nvdl/ _______________________________________________________________________ XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting. [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Or unsubscribe: email@example.com subscribe: firstname.lastname@example.org List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format