OpenSimulator:Xml Serialization - Revision history

Justincc at 18:26, 29 August 2014

2014-08-29T18:26:33Z

2008-01-24T19:36:19Z

‎Draft speculation

2008-01-24T19:34:25Z

‎Draft speculation

2008-01-24T19:27:05Z

‎TextureEntry

2008-01-24T19:19:43Z

‎TextureEntry

2008-01-24T19:19:27Z

‎TextureEntry

2008-01-24T19:18:59Z

‎TextureEntry

2008-01-23T21:10:22Z

‎TextureEntry

2008-01-23T21:03:45Z

‎Node types

2008-01-23T20:56:06Z

‎Draft speculation

← Older revision		Revision as of 18:26, 29 August 2014
Line 1:		Line 1:
		+	'''Note: This proposal is old and proceeded no further.'''
		+
	== Opensimulator Xml Serialization Format 3 ==		== Opensimulator Xml Serialization Format 3 ==
	=== Goals ===		=== Goals ===

@@ Line 12: / Line 12: @@
     Example:
-    <Prim>0 <1.0, 1.0, 1.0> 10 0.5</Prim> could be a way to encapsulate a raw PrimitiveParams dump.
+    <Prim>0 <Vector><X>1.0</X><Y>1.0</Y><Z>1.0</Z></Vector> 10 0.5</Prim> could be a way to encapsulate a raw PrimitiveParams dump.
     <os:Circle extrusion="straight"><Texture ... /></os:Circle>

@@ Line 9: / Line 9: @@
 ===Draft speculation===
-* Since almost all fields have three distinct flavours ("SL GUI values", "LSL PrimitiveParams values" and "Protocol values") we should be able to specify values with units. The default unit should be "Protocol values".
+* Since there is three distinct flavours ("SL GUI values", "LSL PrimitiveParams values" and "Protocol values") of defining prims, we should accomodate for this, quite possibly by having separate tags, so the parser can use that to parse differently.
-What the unit monikers should be is up for anyone to suggest.
-    Alternative 1:
+    Example:
-    <Taper><X>200</X></Taper> means protocol value 200
+    <Prim>0 <1.0, 1.0, 1.0> 10 0.5</Prim> could be a way to encapsulate a raw PrimitiveParams dump.
-   <Taper><X unit="pp">2.0</X></Taper> means LSL value 2.0
+    <os:Circle extrusion="straight"><Texture ... /></os:Circle>
-   <Taper><X unit="ui">-1.0</X></Taper> means SL gui value -1.0
-−
-   Alternative 2:
-   <... taperX="200" ...> protocol 200
-   <... taperX="2.0pp" ...> LSL 2.0
-   <... taperX="-1.0ui" ...> GUI -1.0
-−
-The former is more verbose ('more XML'), the latter terser ('more HTML'). Please do add your opinion.
 * The fields that are enumerated should be encoded as either element types, attribute strings or attribute numbers. The default should be attribute numbers.

@@ Line 42: / Line 42: @@
 ===TextureEntry===
 * The Texture entry should be constructed in line with how the faces are enumerated on an object, ie: every face that is optional in a TextureEntry array, should be defined as an omissible element with one or several 'Face' nodes. If possible, this will make the Texture Face enumeration simpler.
-* [http://wiki.secondlife.com/wiki/Category:LSL_Face Overview of face enumeration]
+* The [http://wiki.secondlife.com/wiki/Category:LSL_Face Overview of LSL face enumeration] although this obviously is LSL biased.
 For example, the 'hollow' will introduce faces only if hollow > 0. Hence, hollow chould be defined as

@@ Line 42: / Line 42: @@
 ===TextureEntry===
 * The Texture entry should be constructed in line with how the faces are enumerated on an object, ie: every face that is optional in a TextureEntry array, should be defined as an omissible element with one or several 'Face' nodes. If possible, this will make the Texture Face enumeration simpler.
-* [[http://wiki.secondlife.com/wiki/Category:LSL_Face Overview of face enumeration]]
+* [http://wiki.secondlife.com/wiki/Category:LSL_Face Overview of face enumeration]
 For example, the 'hollow' will introduce faces only if hollow > 0. Hence, hollow chould be defined as

@@ Line 44: / Line 44: @@
 For example, the 'hollow' will introduce faces only if hollow > 0. Hence, hollow chould be defined as
-    <Hollow size="20%"><Face><Texture src="http://images.tribalmedia.se/textures/plywood.jp2"/></Face></Hollow>
+    <Hollow size="20%"><Face color="#ffdd33"><Texture src="http://images.tribalmedia.se/textures/plywood.jp2"/></Face></Hollow>
 as opposed to
     <... hollow="20%" ...>
 thus allowing the parsing logic to encapsulate what exact faceId the texture should go into.

← Older revision		Revision as of 21:03, 23 January 2008
Line 39:		Line 39:
	* world, scene, avatar, object, part, shape		* world, scene, avatar, object, part, shape
	* texture definitions		* texture definitions
		+
		+	===TextureEntry===
		+	* The Texture entry should be constructed in line with how the faces are enumerated on an object, ie: every face that is optional in a TextureEntry array, should be defined as an omissible element with one or several 'Face' nodes. If possible, this will make the Texture Face enumeration simpler.
		+
		+	For example, the 'hollow' will introduce faces only if hollow > 0. Hence, hollow chould be defined as
		+	<Hollow size="20%"><Face><Texture src="http://images.tribalmedia.se/textures/plywood.jp2"/></Face></Hollow>
		+	as opposed to
		+	<... hollow="20%" ...>
		+	thus allowing the parsing logic to encapsulate what exact faceId the texture should go into.

← Older revision		Revision as of 20:56, 23 January 2008
Line 33:		Line 33:
	<... extrusion="straight" ...> means protocol value 0 (PathCurve.Straight)		<... extrusion="straight" ...> means protocol value 0 (PathCurve.Straight)
	<... extrusion="1" ...> means protocol value 1 (PathCurve.xxx)		<... extrusion="1" ...> means protocol value 1 (PathCurve.xxx)
		+
		+	===Node types===
		+	* entity identifiers (LLUUID vs URI)
		+	* permissions
		+	* world, scene, avatar, object, part, shape
		+	* texture definitions