[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [sdo] List is OSOA Issues for Discussion at this week's meeting
Hi Blaise,
I agree that all the issues that you want to discuss are
indeed valid issues, but I think we should create new JIRAs to discuss them, and
not re-use these old JIRAs just because the names suggest the issues you
describe.
For instance, when I read SDO-23, it seems like there there
is no way through the API to create types. I agree that we need to define
a standard {commonj.sdo}OpenType, but I don't see the connection with the issue,
as it's stated.
Likewise, SDO-24 is talking about serializing SDOs as
binary attachments, but the issue you want to discuss is (I think) how a large
binary property value can be serialized, eg, in a SOAP message, the SDO itself
is still part of the payload but the value of one of the properties is not part
of the payload, but rather an attachment.
We shouldn't be re-using JIRA to discuss issues that are
unrelated to the issues as described in the JIRA... OASIS is supposed to
be open, anyone should be able to read the JIRAs and know what issues we are
discussing.
Perhaps the best way is not to reject the issues, but to
re-word the descriptions so that they fit the topics that we do want to
discuss.
Ron
Von: Blaise Doughan
[mailto:blaise.doughan@oracle.com]
Gesendet: Dienstag, 19. Februar 2008 16:27 An: sdo@lists.oasis-open.org Betreff: Re: [sdo] List is OSOA Issues for Discussion at this week's meeting Hello all,
Below are my thoughts on the proposed issues to be
rejected:
It is true in SDO 2.1 that you can create the
DataObjects that correspond to XML loaded without a schema using DataFactory
(SDO 2.1 section 9.10). The problem with our current solution is that
the Type assigned to these DataObjects is vendor specific. I am ok
with rejecting this issue if we open another one to create a
standardized open sequenced Type.
SDO 24: Support for Attachments
The spirit of this issue was for the efficient
handling of large binary data in DataObjects. I am ok with rejecting this
issue (as web services are out of scope) if we open another issue for the
handling of large binary data in DataObjects for DAS (as DAS is in
scope).
I think we have a partial fix for this in SDO
2.1. Open content properties can have a namespace URI, but the namespace
URI does not factor into aspects of SDO such as XPath/SDO Path access. I
think this issue should remain open to cover the remaining issues.
-Blaise
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]