I see merit of a prim type definition, but then again I believe the oar format may have evolved as a mirror of the schema for the databases used by OpenSim. It may complicate future code if the oar format deviates substantially from these databases. Perhaps the format should reflect the easiest way to transfer content from one OpenSim region to another, regardless of content?
On Tue, Apr 28, 2009 at 5:24 PM, Hurliman, John <john.hurli...@intel.com>wrote: > This is fine if your use case is to consider the prim format I posted as a > canonical format for all virtual world objects, where everything will only > be plus or minus a few fields from that format. I don't think that's going > to be the case moving forward. > > I would prefer to see content-types attached to formats. A Second Life prim > is recognized as application/vnd.ll.primitive, while a realXtend mesh might > be application/x-realxtend-mesh (or something to that effect). That way you > can add support in the future for objects that share very little in common > with Second Life prims. It also fits nicely into larger asset framework > where you can do this type of standardization for notecards, clothing > assets, etc. > > John > > > -----Original Message----- > > From: opensim-dev-boun...@lists.berlios.de [mailto:opensim-dev- > > boun...@lists.berlios.de] On Behalf Of Frisby, Adam > > Sent: Tuesday, April 28, 2009 4:56 PM > > To: opensim-dev@lists.berlios.de > > Subject: Re: [Opensim-dev] Standardizing OpenSim data formats > > > > The parser needs to not barf if it sees an unknown element in there. > > Eg, ModRex mesh parameters, etc. > > > > Ideally the SaveToXYZ function should fire an event on the object > > called something like say 'OnSaveRequest(out List<???> extraData)' > > which allows other modules to save additional data. On-load/On- > > construct should probably also fire an event which allows the data to > > be restored. > > > > Adam > > > >> -----Original Message----- > >> From: opensim-dev-boun...@lists.berlios.de [mailto:opensim-dev- > >> boun...@lists.berlios.de] On Behalf Of Hurliman, John > >> Sent: Tuesday, 28 April 2009 4:32 PM > >> To: opensim-dev@lists.berlios.de > >> Subject: [Opensim-dev] Standardizing OpenSim data formats > >> > >> Currently, OpenSim server<->server communication is primarily made up > >> of .NET XML serialization. As a side effect of this, I've seen the wire > >> format between simulator and grid services or grid service to grid > >> service change many times since I started working on backend services. > >> The OAR file format has also changed at least once while retaining the > >> same version number because the underlying prim XML format changed. I > >> am working on a libomv OAR reader/writer at the moment, and trying to > >> deal with hacks for supporting pre and post change OAR files. > >> > >> To increase compatibility between versions of OpenSim and with third > >> party services I'd like to propose a standardization of (eventually) > >> all over-the-wire communication in OpenSim. I started with an > >> attempt at an LLIDL definition for primitives: > >> > >> http://opensimulator.org/wiki/PrimitiveFormatProposal > >> > >> Is anything missing? Does this look like a reasonable start? > >> > >> John > >> _______________________________________________ > >> Opensim-dev mailing list > >> Opensim-dev@lists.berlios.de > >> https://lists.berlios.de/mailman/listinfo/opensim-dev > > _______________________________________________ > > Opensim-dev mailing list > > Opensim-dev@lists.berlios.de > > https://lists.berlios.de/mailman/listinfo/opensim-dev > _______________________________________________ > Opensim-dev mailing list > Opensim-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/opensim-dev >
_______________________________________________ Opensim-dev mailing list Opensim-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/opensim-dev
