Talk:XML - Revision history

Jukeboksi: relink

2004-03-18T12:48:19Z

relink

← Older revision		Revision as of 12:48, 18 March 2004
Line 7:		Line 7:
	I've had tremendous trouble trying to figure out how to express [[Product group]]s in generic markup. The idea is that all [[product]]s belong to a [[product group]] and that [[product group]]s can belong to other [[product group]]s. [[tomatoe]]s are [[vegeatable]]s, which are [[food]] etc.		I've had tremendous trouble trying to figure out how to express [[Product group]]s in generic markup. The idea is that all [[product]]s belong to a [[product group]] and that [[product group]]s can belong to other [[product group]]s. [[tomatoe]]s are [[vegeatable]]s, which are [[food]] etc.

	The idea is to allow the defining of different relationships between [[product group]]s, for the uses of describing [[Product substitution]]s and [[~~Production Flow~~]]s and other stuff we haven't even thought of yet.		The idea is to allow the defining of different relationships between [[product group]]s, for the uses of describing [[Product substitution]]s and [[sevice cycle]]s and other stuff we haven't even thought of yet.

	I was aiming at a generic [[product group]]-element to make the processing software ([[Instructional capital]]) simpler, but I can't get it to work. We could have an generic [[product group]]-element that encapsulates group specific data in a more specific element like:		I was aiming at a generic [[product group]]-element to make the processing software ([[Instructional capital]]) simpler, but I can't get it to work. We could have an generic [[product group]]-element that encapsulates group specific data in a more specific element like:

Jukeboksi: relink

2004-03-18T12:47:33Z

relink

← Older revision		Revision as of 12:47, 18 March 2004
Line 17:		Line 17:
	Using "ANY"-constraint (can contain any element... or is it even #PCDATA??) can be kind of hazardous for software.. but maybe we just add these specific groups so that each element can contain just one of the available subgroups for this subgroup.		Using "ANY"-constraint (can contain any element... or is it even #PCDATA??) can be kind of hazardous for software.. but maybe we just add these specific groups so that each element can contain just one of the available subgroups for this subgroup.

	But this would not allow to define variable relationships required to give everyone their say about [[product substitution]] and [[~~production flow~~]]...		But this would not allow to define variable relationships required to give everyone their say about [[product substitution]] and [[service cycle]]...

	I don't know... We need XML-gurus		I don't know... We need XML-gurus

142.177.74.86 at 17:55, 26 February 2004

2004-02-26T17:55:16Z

← Older revision		Revision as of 17:55, 26 February 2004
Line 25:		Line 25:

	: let's start it off with a small collection of schemas, say { resource.xsd, person.xsd, a product.xsd, service.xsd }.		: let's start it off with a small collection of schemas, say { resource.xsd, person.xsd, a product.xsd, service.xsd }.

			---------

			Sourceforge entry needs a LOT more links and information. Like at least a real link to Consumerium!

216.130.212.63: get it rolling

2003-07-01T16:41:13Z

get it rolling

← Older revision		Revision as of 16:41, 1 July 2003
Line 12:		Line 12:
	<product_group id=??><food_group id=??>...</food_group></product_group>		<product_group id=??><food_group id=??>...</food_group></product_group>
	<product_group id=??><clothing_group id=??>...</clothing_group></product_group>		<product_group id=??><clothing_group id=??>...</clothing_group></product_group>

			: start simple. define a relationship between a set of objects with a group markup tag, e.g.: <group name="bread"> <fu/> <bar/> </group> establishes a named relationship betwen <fu/> and <bar/>. let the group tag have anything inside it, including text. treat it as markup.

	Using "ANY"-constraint (can contain any element... or is it even #PCDATA??) can be kind of hazardous for software.. but maybe we just add these specific groups so that each element can contain just one of the available subgroups for this subgroup.		Using "ANY"-constraint (can contain any element... or is it even #PCDATA??) can be kind of hazardous for software.. but maybe we just add these specific groups so that each element can contain just one of the available subgroups for this subgroup.
Line 18:		Line 20:

	I don't know... We need XML-gurus		I don't know... We need XML-gurus
			: do you want to markup text? or do you want to define structure? or both?

			: DTD syntax is troublesome and difficult to master. the newer xml schema is itself xml, and is capable of a whole lot more... it could make expression of your product group easier.

			: let's start it off with a small collection of schemas, say { resource.xsd, person.xsd, a product.xsd, service.xsd }.

Jukeboksi: Thiking about XML design priciples I come to the conclusion that WE NEED XML-GURUS!!!

2003-06-15T16:11:47Z

Thiking about XML design priciples I come to the conclusion that WE NEED XML-GURUS!!!

New page

==XML design principles==
...

==XML design problems==
===[[Product group]]===
I've had tremendous trouble trying to figure out how to express [[Product group]]s in generic markup. The idea is that all [[product]]s belong to a [[product group]] and that [[product group]]s can belong to other [[product group]]s. [[tomatoe]]s are [[vegeatable]]s, which are [[food]] etc.

The idea is to allow the defining of different relationships between [[product group]]s, for the uses of describing [[Product substitution]]s and [[Production Flow]]s and other stuff we haven't even thought of yet.

I was aiming at a generic [[product group]]-element to make the processing software ([[Instructional capital]]) simpler, but I can't get it to work. We could have an generic [[product group]]-element that encapsulates group specific data in a more specific element like:
<product_group id=??><food_group id=??>...</food_group></product_group>
<product_group id=??><clothing_group id=??>...</clothing_group></product_group>

Using "ANY"-constraint (can contain any element... or is it even #PCDATA??) can be kind of hazardous for software.. but maybe we just add these specific groups so that each element can contain just one of the available subgroups for this subgroup.

But this would not allow to define variable relationships required to give everyone their say about [[product substitution]] and [[production flow]]...

I don't know... We need XML-gurus