DAP4 Attribute Model - Revision history

Ndp: /* Background */

2009-09-23T18:25:03Z

Background

← Older revision		Revision as of 18:25, 23 September 2009
Line 14:		Line 14:

	:'''''is-a''''' expresses that the relationship its parent DAP object has towards it as "Is a". As in: My parent is another representation of the thing that I represent.		:'''''is-a''''' expresses that the relationship its parent DAP object has towards it as "Is a". As in: My parent is another representation of the thing that I represent.


			The discussion here: https://cf-pcmdi.llnl.gov/trac/ticket/27 is relevant.

	=== Design ===		=== Design ===

Ndp: /* Example Document */

2009-01-28T19:42:22Z

Example Document

← Older revision		Revision as of 19:42, 28 January 2009
Line 706:		Line 706:
	<Grid name="u">		<Grid name="u">
	<OtherXML relationship="has-a">		<OtherXML relationship="has-a">
	<~~foo~~ xmlns="http://www.opengis.net/WxS />		<units xmlns="http://www.opengis.net/WxS />
	</OtherXML >		</OtherXML >
	< OtherXML relationship="is-a" >		< OtherXML relationship="is-a" >

Ndp: /* Example Document */

2009-01-28T19:32:41Z

Example Document

← Older revision		Revision as of 19:32, 28 January 2009
Line 137:		Line 137:
	<Grid name="u">		<Grid name="u">
	<Attribute name="one" type="OtherXML" relationship="has-a">		<Attribute name="one" type="OtherXML" relationship="has-a">
	<~~foo~~ xmlns="http://my.foo.com/ns/~~foo~~#" />		<units xmlns="http://my.foo.com/ns/units#" />
	</Attribute>		</Attribute>
	<Attribute name="two" type="OtherXML" relationship="is-a">		<Attribute name="two" type="OtherXML" relationship="is-a">

Ndp: /* Background */

2009-01-28T19:23:07Z

Background

← Older revision		Revision as of 19:23, 28 January 2009
Line 13:		Line 13:
	With the introduction of more complex metadata into the DAP the possibility for another relationship now exists: '''''is-a'''''		With the introduction of more complex metadata into the DAP the possibility for another relationship now exists: '''''is-a'''''

	:'''''is-a''''' expresses that the relationship its parent DAP object has towards it as "Is a". As in: My parent is another representation of the ~~(top)~~ thing that I represent.		:'''''is-a''''' expresses that the relationship its parent DAP object has towards it as "Is a". As in: My parent is another representation of the thing that I represent.

	=== Design ===		=== Design ===

BennoBlumenthal: /* Background */

2009-01-28T19:22:12Z

Background

← Older revision		Revision as of 19:22, 28 January 2009
Line 13:		Line 13:
	With the introduction of more complex metadata into the DAP the possibility for another relationship now exists: '''''is-a'''''		With the introduction of more complex metadata into the DAP the possibility for another relationship now exists: '''''is-a'''''

	:'''''is-a''''' expresses that the relationship its parent DAP object has towards it as "Is a". As in: My parent ~~can be seen as having~~ the ~~same semantics as the thing~~(s) that I represent.		:'''''is-a''''' expresses that the relationship its parent DAP object has towards it as "Is a". As in: My parent is another representation of the (top) thing that I represent.

	=== Design ===		=== Design ===

Ndp: /* Example Document */

2009-01-28T19:10:49Z

Example Document

← Older revision		Revision as of 19:10, 28 January 2009
Line 183:		Line 183:

	----		----



	~~----~~
	While this works to include foreign xml in the DAP, I think we would be better off if we had some stronger semantics than "attribute" availabe. In particular, I think we need to say in this particular example that the XML enclosed is an alternate description of the node in question, i.e. a dataset is an wcs CoverageDescription and a Grid is a wcs:Field. We need that connection in order to build the code that moves data from one representation to another, e.g. build a WCS response from DAP data.

	~~One possibility would be a property dap:alsoKnownAs.~~

	~~--[[User:BennoBlumenthal\|BennoBlumenthal]] 08:03, 25 January 2009 (PST)~~

	== Re-factoring the representation of DAP Attribute objects. ==		== Re-factoring the representation of DAP Attribute objects. ==

Ndp: /* Background */

2009-01-28T19:10:05Z

Background

← Older revision		Revision as of 19:10, 28 January 2009
Line 7:		Line 7:
	=== Background ===		=== Background ===

	Until now the DAP Attribute model has held the (not formally encoded) assumption that all DAP Attribute objects "belong" to the DAP Variable or DAP Attribute that contains them: "The variable ''x'' has an Attribute called ''foo''." This is what we will call a '''''~~HasA~~''''' relationship.		Until now the DAP Attribute model has held the (not formally encoded) assumption that all DAP Attribute objects "belong" to the DAP Variable or DAP Attribute that contains them: "The variable ''x'' has an Attribute called ''foo''." This is what we will call a '''''has-a''''' relationship.

	:'''''~~HasA~~''''' expresses that the relationship its parent DAP object has towards it as "Has A". As in: My parent has the propert(y \| ies) that I represent.		:'''''has-a''''' expresses that the relationship its parent DAP object has towards it as "Has a". As in: My parent has the propert(y \| ies) that I represent.

	With the introduction of more complex metadata into the DAP the possibility for another relationship now exists: '''''~~IsA~~'''''		With the introduction of more complex metadata into the DAP the possibility for another relationship now exists: '''''is-a'''''

	:'''''~~IsA~~''''' expresses that the relationship its parent DAP object has towards it as "Is A". As in: My parent can be seen as having the same semantics as the thing(s) that I represent.		:'''''is-a''''' expresses that the relationship its parent DAP object has towards it as "Is a". As in: My parent can be seen as having the same semantics as the thing(s) that I represent.

	=== Design ===		=== Design ===

Ndp: /* Design */

2009-01-28T19:09:13Z

Design

← Older revision		Revision as of 19:09, 28 January 2009
Line 70:		Line 70:
	#* A value of '''''is-a''''' expresses that the relationship of the Attribute object's parent DAP object has towards the Attribute objects content as "Is A". As in: My parent can be seen as having the same semantics as the thing(s) that I contain.		#* A value of '''''is-a''''' expresses that the relationship of the Attribute object's parent DAP object has towards the Attribute objects content as "Is A". As in: My parent can be seen as having the same semantics as the thing(s) that I contain.

	In ~~essence,~~ the OtherXML Attribute type is invisible (thus the reasoning behind it being nameless). ~~Both of these issues can be addressed in the proposed changes to the XML representation of Attributes below.~~		The OtherXML type is essentially a nameless wrapper that defines the relationship between it's parent container and it's contents. In a sense the OtherXML Attribute type is invisible (thus the reasoning behind it being nameless).


			Both of these issues can be addressed in the proposed changes to the XML representation of Attributes below.

	(''Since this change is taking place in conjunction with re-factoring the XML representation of DAP Attribute objects this new Attribute type will be included those sections.'')		(''Since this change is taking place in conjunction with re-factoring the XML representation of DAP Attribute objects this new Attribute type will be included those sections.'')

Ndp: /* Schema Snippet */

2009-01-27T22:46:15Z

Schema Snippet

← Older revision		Revision as of 22:46, 27 January 2009
Line 35:		Line 35:
	<xs:attribute name="name" type="xs:string" use="required"/>		<xs:attribute name="name" type="xs:string" use="required"/>
	<xs:attribute name="type" type="dap2:DataType" use="required"/>		<xs:attribute name="type" type="dap2:DataType" use="required"/>
	<xs:attribute name="relationship" type="relationships" use="optional" default="has-a"/>		'''<xs:attribute name="relationship" type="relationships" use="optional" default="has-a"/>'''
	</xs:complexType>		</xs:complexType>

Line 41:		Line 41:

	-->		-->
	<xs:simpleType name="relationships">		'''<xs:simpleType name="relationships">'''
	<xs:restriction base="xs:string">		'''<xs:restriction base="xs:string">'''
	<xs:enumeration value="is-a"/>		'''<xs:enumeration value="is-a"/>'''
	<xs:enumeration value="has-a"/>		'''<xs:enumeration value="has-a"/>'''
	</xs:restriction>		'''</xs:restriction>'''
	</xs:simpleType>		'''</xs:simpleType>'''

	== Add a DAP Attribute with type ''OtherXML''. ==		== Add a DAP Attribute with type ''OtherXML''. ==

Ndp: /* Design */

2009-01-27T22:45:17Z

Design

← Older revision		Revision as of 22:45, 27 January 2009
Line 69:		Line 69:
	#* A value of '''''has-a''''' expresses the relationship of the Attribute object's parent DAP object has towards the Attribute objects content as "Has A". As in: My parent has the propert(y \| ies) that I contain.		#* A value of '''''has-a''''' expresses the relationship of the Attribute object's parent DAP object has towards the Attribute objects content as "Has A". As in: My parent has the propert(y \| ies) that I contain.
	#* A value of '''''is-a''''' expresses that the relationship of the Attribute object's parent DAP object has towards the Attribute objects content as "Is A". As in: My parent can be seen as having the same semantics as the thing(s) that I contain.		#* A value of '''''is-a''''' expresses that the relationship of the Attribute object's parent DAP object has towards the Attribute objects content as "Is A". As in: My parent can be seen as having the same semantics as the thing(s) that I contain.
	In essence, ~~this~~ Attribute type is invisible (thus the reasoning behind it being nameless). ~~both~~ of these issues can be addressed in the proposed changes to the XML representation of Attributes below.
			In essence, the OtherXML Attribute type is invisible (thus the reasoning behind it being nameless). Both of these issues can be addressed in the proposed changes to the XML representation of Attributes below.