Hi Frank,
One other point that has been made in the Apr-29 call
was whether the notion of "element(or attribute)-backed" is valid for SDO
path. After all, if the SDO name of the property doesn't show up in the path and
if the element/attribute duality does surface, then your path is simply an XPath
(or subset thereof): problem solved.
Radu
From: Bryan Aupperle
[mailto:]
Sent: Monday, May 05, 2008 5:12
AM
To:
Subject: Re: [sdo]
[ServiceDataObjects] SDO-71
I believe Issue 85 -
Section 9.10 needs rules for handling elements and attributes with the
same name (http://www.osoa.org/jira/browse/SDO-85) can be used for the attribute/element name overlap.
I like the proposal below.
Bryan Aupperle, Ph.D.
STSM, WebSphere
Enterprise Platform Software Solution Architect
Research Triangle Park,
NC
+1 919-254-7508 (T/L 444-7508)
Internet Address:
Frank Budinsky
<>
05/04/2008 11:00 PM
To
cc
Subject
[sdo] [ServiceDataObjects]
SDO-71
Hi Guys,
Sorry I missed last weeks call. Fuhwei updated me on
the discussion you
had about SDO-71. I understand the issue raised and
agree that we should
open another issue to consider the possibly of
defining a standard name
conflict resolution algorithm. However, I believe
the following modified
proposal for SDO-71 should be considered
independently.
Proposal:
"name" will bind to an element-backed
property named "foo" but will also
match an attribute-backed "foo"
property if there is no conflicting
element-backed property. "@foo" binds
to an attribute-backed property with
XML name "foo".
Note that with
this proposal "@foo" could map to a property with a mangled
name (e.g.,
"foo_attribute") in the case of duplicates. The mangling
algorithm can be
implementation dependent or, if we decide to, can be
standardized. This
proposal would, however, be unaffected by the
resolution of that
issue.
Thanks,
Frank
Frank
Budinsky/Toronto/IBM@IBMCA
04/28/2008 10:37
AM
To
cc
Subject
Re: [sdo]
Groups - OASIS SDO TC Weekly Teleconference
modified
Hi Ron,
Can we please also add
SDO-71 (SDOPath handling of '@' character) to this
weeks agenda? It's a
pretty simple issue, that I think can be resolved
quickly. The proposal in
the JIRA is:
1. If a DataObject's Type is backed by an XSD complex type
that contains
an attribute and element with the same name, then "@name"
binds to the
attribute-backed property and "name" will bind to the the
element-backed
property.
Another alternative which I believe is
slightly simpler and in line with
the intent of "@name" in
XPath.
2. "@name" binds to attribute-backed properties only. "name"
will bind to
the the element-backed property first but will also match an
attribute-backed property if there is no conflciting element-backed
property.
This second proposal is not 100% backward compatible
("@name" would no
longer match an element-backed property), but my guess
is that nobody
would ever have wanted to use it that way anyway. The
convienince is the
other way around - users want to be able to access
either attributes or
elements with the simple
"name".
Thanks,
Frank
04/28/2008 08:58
AM
To
cc
Subject
[sdo] Groups
- OASIS SDO TC Weekly Teleconference
modified
OASIS SDO TC Weekly Teleconference has
been modified by Mr. Ron Barack
Date: Tuesday, 29 April
2008
Time: 12:00pm - 01:00pm ET
Event Description:
Call in
Details:
Germany +49 69 210 869 100 or 0800 455 6556
Australia
1800 136 708
Austria +43 1 928 1440 0800 298 662
Belgium +32 2 400
6921 0800 74569
Brasil 0800 891 4822
Canada +1 5143157880 1 8888 201
142
China (North) 1 0800 749 0080
China (South) 1 0800 490 0067
Croatia 0800 222707
Czech Rep. 800 143 199
Denmark 8088 3307
Finland 0800 914 769
France +33 170 729 898 or 0800 908 390
Hungary 06 800 137 97
India 000 800 100 6136
Ireland +353 15260013
1 800 555 072
Israel 1809 349 047
Italy +39 023 604 9151 800 788 754
Japan 0034 800 400 914
Netherlands +31 207947923 or 08000 249 970
Norway 800 148 38
Philippines 1800 149 10 004
Poland 00800 4911555
Portugal +351 211209552 800 849 176
Russia 810 800 212 81 049
Romania 0800 895024
Singapore 800 492 2115
Slovakia 08000 490 08
South Africa 0 800 980 958
Spain +34 914 142 196 or 900 994 999
Sweden +46 850 564 731 or 020 791 212
Switzerland +41 44 580 1003 or
0800 890 007
UK +44 207 075 3204 or 0808 234 1757
USA +1 215 305 4494
or 1 866 203 4642
Participant Code: 159475
Chat room:
http://webconf.soaphub.org/conf/room/sdo-TC
WebConference:
http://sap.webex.com/sap
Meeting Number: 747 969 851
Meeting Password:
sdosdosdo
Agenda:
I. Intro
a. Roll Call
b. Assignment/
Confirmation of Scribe
c. Agenda Bashing
d. Approval of last week's
minutes.
http://www.oasis-open.org/apps/org/workgroup/sdo/download.php/28054/SDO%20TC%20Meeting%20minutes%20-%2022%20April%202008.txt
II.
Accepting new issues
Two of the issues that Blaise proposed were never
formally accepted or
rejected.
SDO-126: Define the concept
Containment
http://www.osoa.org/jira/browse/SDO-126
SDO-128: Allow
Properties to Have Composite Keys
http://www.osoa.org/jira/browse/SDO-128
III. OpenCSA Liason
Committee status, and representative.
We should choose a
representative to the OPEN CSA Liason Committee
Charter is
here:
http://www.oasis-open.org/apps/org/workgroup/opencsa-ms/download.php/28090/OpenCSA%20InterTC%20-%20Subcommittee-Charter-20080411dr2.doc
IV.
Discussion of SDO-124
I would like to focus on
understanding Oracle's approach.
Because of some technical
problems associated with Progress
Software's purchase of Xcalia, I am not
sure if Eric, Christophe or
Francois will be able to attend.
Therefore, it might be difficult to
discuss the Technical Root
proposal. In fact, the absense of these
members may be reason to
delay the containment discussion until the
membership problems have been
straightend out.
V. ISSUE 5: Defining SDO types by JAVA
types
Last email:
http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/200804/msg00039.html
Minutes:
This
event is one in a list of recurring events.
Other event dates in this
series:
Tuesday, 04 December 2007, 12:00pm to 01:00pm ET
Tuesday, 11
December 2007, 12:00pm to 01:00pm ET
Tuesday, 18 December 2007, 12:00pm to
01:00pm ET
Tuesday, 25 December 2007, 12:00pm to 01:00pm ET
Tuesday, 01
January 2008, 12:00pm to 01:00pm ET
Tuesday, 08 January 2008, 12:00pm to
01:00pm ET
Tuesday, 15 January 2008, 12:00pm to 01:00pm ET
Tuesday, 22
January 2008, 12:00pm to 01:00pm ET
Tuesday, 29 January 2008, 12:00pm to
01:00pm ET
Tuesday, 05 February 2008, 12:00pm to 01:00pm ET
Tuesday, 12
February 2008, 12:00pm to 01:00pm ET
Tuesday, 19 February 2008, 12:00pm to
01:00pm ET
Tuesday, 26 February 2008, 12:00pm to 01:00pm ET
Tuesday, 04
March 2008, 12:00pm to 01:00pm ET
Tuesday, 11 March 2008, 12:00pm to
01:00pm ET
Tuesday, 18 March 2008, 12:00pm to 01:00pm ET
Tuesday, 25
March 2008, 12:00pm to 01:00pm ET
Tuesday, 01 April 2008, 12:00pm to
01:00pm ET
Tuesday, 08 April 2008, 12:00pm to 01:00pm ET
Tuesday, 15
April 2008, 12:00pm to 01:00pm ET
Tuesday, 22 April 2008, 12:00pm to
01:00pm ET
Tuesday, 06 May 2008, 12:00pm to 01:00pm ET
Tuesday, 13 May
2008, 12:00pm to 01:00pm ET
Tuesday, 20 May 2008, 12:00pm to 01:00pm
ET
Tuesday, 27 May 2008, 12:00pm to 01:00pm ET
View event
details:
http://www.oasis-open.org/apps/org/workgroup/sdo/event.php?event_id=17148
PLEASE
NOTE: If the above link does not work for you, your email
application
may be breaking the link into two pieces. You may be able to
copy and
paste the entire link address into the address field of your
web
browser.
[attachment "ical_17148.ics" deleted by Frank
Budinsky/Toronto/IBM]
---------------------------------------------------------------------
To
unsubscribe from this mail list, you must leave the OASIS TC that
generates
this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To
unsubscribe from this mail list, you must leave the OASIS TC that
generates
this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To
unsubscribe from this mail list, you must leave the OASIS TC that
generates
this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
