Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

business object definitions

 [1/11] from: robert:muench:robertmuench at: 5-Oct-2001 10:13


> -----Original Message----- > From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]On Behalf Of
<<quoted lines omitted: 5>>
> would give a common base to store this information along the lines of IBMs > SanFransico business objects (although hopefully less complicated).
Hi, I hope so ;-). We should make it KISS and Rebol abillity to extend objects, using the XML approach: if you don't understand it just ignore it etc. With this we should get a simple loose coupled collection of objects.
> I have to admit, I wouldn't know where to start in designing all this :)
Hmm... I would like to use an application like the knowledge base contained in /Link. Where everyone can comment on objects, data fields, functions etc. For each object, there should exist an object-owner, who manages and coordinates the information. From time to time there should be a feature freeeze and a stable object definition should be released. IMO a how-to style document per object, which describs the object etc. might be helpful. Robert

 [2/11] from: media:quazart at: 5-Oct-2001 10:18


I've been advocating having a Library (NOT sources, but function libraries) and object site for a while. I am just about to start (finally) coding such a project! I am still looking for a web host (with rebol cgi), but Am about to start work on xwire... so It will be working internally for until then. The project is not completely defined, I'm listening to this list for the ideas all the time. The only Cemented thing so far is that people will be able to reserve and register a prefix to use on function libraries. this will permit everyone to code SAFELY. Anyone using his prefix will allow any other user to code using his stuff without problems. this is especially usefull when working on utilities... imagine if everyone has different tools for printing and they start calling them "aprint" "zprint" or whatever... you quickly run into problems. Once a poster has registered his prefix (which is a public list), he can post his stuff right away and handle the versioning and stuff like that. I forgot, but another thing which will be mandatory is that a document of whatever type is supplied with the tools. The upload will specify if its extensive or short, but some amout of documentation is necessary. I've noted that code without documentation isn't very popular... so there is no point in sharing it if its going to deaf ears... I have had some good feedback so far, anyone wishing to help is welcomed, although at this point it is still in the form of ideas and comments. Please send ANY comments to [moliad--hotmail--com]. The other point of note is that I wish to use this list as the point of sharing for the tools. One or two mails a week to let the community in on what is happening on the shared site. -Max

 [3/11] from: greggirwin:starband at: 5-Oct-2001 11:29


Hi Max, Chris Morency and I have been discussing soemthing along the same lines. We should all stay in touch to reduce duplicated effort. --Gregg

 [4/11] from: greggirwin:starband at: 5-Oct-2001 11:40


Hi Robert, << I would like to use an application like the knowledge base contained in /Link. Where everyone can comment on objects, data fields, functions etc. >> I don't have /Link, I can't comment on it directly, but here's a thought I had, which I told Chris Morency about as it would relate to a centralized function library. If IOS needs to be tested, and we want to prove its fitness for RTCC (Real Time Collaborative Computing), how can we get something set up to use it? RT? What would it take to set it up? What about collaborative development tools that are truly "real time"? Can you say REBOLForge? :) The key, I think, is IOS. --Gregg

 [5/11] from: jseq::mediaone::net at: 5-Oct-2001 10:20

Re: business object definitions/where to start


A good place to start for the business object definitions would be vCard/vCal. These are standards for contact and calendar information. They're not super well known, but I believe most PIMs can read/write them (Outlook definitely can). They have a plain text representation as well as an XML representation. Also, for more generic business objects, the two initiatives with the most traction are RosettaNet and ebXML. I'm not sure of the relative merits, but their specs might prove useful as starting points. If you piggyback your efforts on prior art, converting XML representations into native REBOL, you'll bootstrap it a lot faster and retain some sense of inter-system compatibility. An emerging initiative, that takes the approach I'm recommending is the Universal Business Lanugage http://www.oasis-open.org/committees/ubl/ Very new (just announced), but pretty close in aims to what I think you're trying to accomplish. John
> To: [rebol-list--rebol--com] > > Subject: [REBOL] Re: IOS data
<<quoted lines omitted: 17>>
> document per > object, which describs the object etc. might be helpful. Robert
-- Binary/unsupported file stripped by Listar -- -- Type: text/x-vcard -- File: John Sequeira.vcf

 [6/11] from: phil:hayes:cnutarch at: 5-Oct-2001 19:25


Not that I'm a great lover of XML but http://www.syncml.org/ details some schemas for vCARD etc...

 [7/11] from: deryk:iitowns at: 6-Oct-2001 11:04


On Friday 05 October 2001 14:25, you wrote:
> Not that I'm a great lover of XML but http://www.syncml.org/ details some > schemas for vCARD etc...
Better yet are the RFCs: vCard: 2425, 2426 vCal (iCal): 2445, 2446, 2447 Best to build on the framework than from the top down IMO.

 [8/11] from: robert:muench:robertmuench at: 6-Oct-2001 10:27


> -----Original Message----- > From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]On Behalf Of
<<quoted lines omitted: 5>>
> traction are RosettaNet and ebXML. I'm not sure of the relative merits, > but their specs might prove useful as starting points.
Hi, there are a zillion of different "standards" out there. I know some of them and most of them are much to complicate without being very useful. A lot initiatives try to solve all problems instead of focusing on the relevant things.
> If you piggyback your efforts on prior art, converting XML representations > into native REBOL, you'll bootstrap it a lot faster and retain some sense > of inter-system compatibility.
It's OK to take some of the ideas. IMO we don't need to create portable definitions as I'm just interested in the Rebol part, if others want to use these too, well let them convert the Rebol datatypes.
> An emerging initiative, that takes the approach I'm recommending is the > Universal Business Lanugage
Thanks for the tip, never heard about it. I would like to see a simple approach to get things working fast, get a feeling for the whole process, and maybe start over again with the experience made. There won't be to much work lost. Robert

 [9/11] from: robert:muench:robertmuench at: 6-Oct-2001 10:27

Re: business object definitions


> -----Original Message----- > From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]On Behalf Of
<<quoted lines omitted: 3>>
> Subject: [REBOL] Re: business object definitions > The key, I think, is IOS.
Hi, I don't know much about IOS at the moment and it might take some time to arrive. Therefore I take what I have at hand and IMO it's sufficient to get started. The collection of business-object descriptions should be "technology" independent (in the way, that it doesn't matter, which Rebol part we use). Robert

 [10/11] from: greggirwin:starband at: 6-Oct-2001 11:45


Hi Robert, << I don't know much about IOS at the moment and it might take some time to arrive. Therefore I take what I have at hand and IMO it's sufficient to get started. The collection of business-object descriptions should be technology independent (in the way, that it doesn't matter, which Rebol part we use).
>>
Agreed. I'm not saying we should use IOS for delpoyment purposes but, rather, as a collaboration tool for *us* to use while designing things. Something a little better than just using the mailing list. We could also set up a Yahoo group, but I think this kind of thing is exactly what IOS is for. As people from RT point out, they couldn't do what they do without REBOL, so let's think like they do. :) --Gregg

 [11/11] from: robert:muench:robertmuench at: 8-Oct-2001 12:12


> -----Original Message----- > From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]On Behalf Of
<<quoted lines omitted: 4>>
> Agreed. I'm not saying we should use IOS for delpoyment purposes but, > rather,as a collaboration tool for *us* to use while designing things.
Hi Gregg, ah ok I see. With this you have my full support :-)). The process I would suggest with traditional tools is: 1. Setup a Web-Forum/Mailinglist to discuss things 2. Setup a project home page to document the results from the discussion 3. Nominate at least one Processowner. This person will consolidate the results every 7-14 days and integrate them into the project home site. 4. Let the discussion go for 2-4 weeks, make a feature-freeze and a documentation release and continue with a 2-4 week schedule. Robert

Notes
  • Quoted lines have been omitted from some messages.
    View the message alone to see the lines that have been omitted