[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

sdef schema: implementation element

Subject: sdef schema: implementation element
From: Philip Aker <email@hidden>
Date: Tue, 24 Jul 2007 06:01:15 -0700
Delivered-to: email@hidden
Delivered-to: email@hidden

The notion of extending the sdef implementation element for other technologies was discussed briefly in another thread and a bit more off-list.

Here's one way to define the extension formally in an XML Schema for sdefs that can handle both 'cocoa' elements as they are currently used plus additional implementations.

The attributes for the example 'carbon' element are not carved in stone -- the general idea being to allow a flexible symbol lookup for Carbon Events and/or a search for an AppleEvent handler and to provide a parameter list for 'get' and 'set' query events. In this example, the 'parameter-types' would be key/value pairs ('----' 'utxt' e.g.).

Note that other languages such as java, ruby, etc. can use a similar notion provided they are willing to do the xml grunt work to parse up the parent chain to get whatever element/attribute relationships they need.

<!-- sdef.xsd -->

<!-- ... -->

<!-- IMPLEMENTATION ELEMENTS -->

<xsd:element name="implementation" abstract="true"/>
<xsd:element name="cocoa" substitutionGroup="implementation">
	<xsd:complexType>
		<xsd:attribute name="name" type="xsd:NMTOKEN"/>
		<xsd:attribute name="class" type="xsd:NMTOKEN"/>
		<xsd:attribute name="key" type="xsd:NMTOKEN"/>
		<xsd:attribute name="method" type="xsd:NMTOKEN"/>
	</xsd:complexType>
</xsd:element>

<xsd:element name="carbon" substitutionGroup="implementation">
	<xsd:complexType>
		<xsd:attribute name="handler" type="xsd:NMTOKEN"/>
		<xsd:attribute name="event-class" type="OSType"/>
		<xsd:attribute name="event-id" type="OSType"/>
		<xsd:attribute name="parameter-types" type="OSTypes"/>
		<xsd:attribute name="result-type" type="OSType"/>
		<xsd:attribute name="description" type="Text"/>
	</xsd:complexType>
</xsd:element>

Much appreciated if you have comments on the above or suggestions for what other languages could use before I file an enhancement bug.

Philip Aker
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-implementors mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-implementors/email@hidden

This email sent to email@hidden

Prev by Date: Re: Element "initializers"
Next by Date: NSReceiverEvaluationScriptError: 4 when I try to access an attribute of a newly created object.
Previous by thread: Slightly OT: Some testers?
Next by thread: NSReceiverEvaluationScriptError: 4 when I try to access an attribute of a newly created object.
Index(es):
- Date
- Thread

Home