Re: [sca-assembly] A few questions on the SCA proprty values

[Mike Edwards <mike_edwards@uk.ibm.com>]

Anish,

There are a number of differences between
the way in which a value can be expressed on a <component/> <property/>
from the way a value can be expressed
on a <composite/> <property/>

I note that there is a very close parallel
between <composite/>  <property/> and <componentType/>
<property/>, and
perhaps there was a desire to keep the
latter as simple as possible.   In general, values are intended to
be set by
component properties and it is these
that are given the full panoply of choices.

However, you ask a reasonable question
- you might like to raise an issue to add extra ways of specifying values
on
<composite/> <property/>
elements...


Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com

From:	Anish Karmarkar <Anish.Karmarkar@oracle.com>
To:
Cc:	sca-assembly@lists.oasis-open.org
Date:	11/08/2009 08:08
Subject:	Re: [sca-assembly] A few questions on the SCA proprty values

---

+1

In addition, I noticed that the file attribute is allowed for component
properties but not composite properties. Any particular reason why this
is so?

-Anish
--

David Booz wrote:
> Hopefully someone is going to open an issue for the points below.
In 
> addition, we should also clarify how the prop1.txt file itself is
> resolved. For example, if the URI pointing to the file is relative,
it 
> should be relative to the contribution which contains the composite
that 
> is referencing the file.
> 
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC and SCA-J TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:booz@us.ibm.com
> 
> Inactive hide details for Mike Edwards ---08/04/2009 04:28:40 
> AM---Raymond, Responses inlineMike Edwards ---08/04/2009 04:28:40
> AM---Raymond, Responses inline
> 
> 
> From:                
> Mike Edwards <mike_edwards@uk.ibm.com>
> 
> To:                
> sca-assembly@lists.oasis-open.org
> 
> Date:                
> 08/04/2009 04:28 AM
> 
> Subject:              
  
> Re: [sca-assembly] A few questions on the SCA proprty values
> 
> ------------------------------------------------------------------------
> 
> 
> 
> 
> Raymond,
> 
> Responses inline
> 
> Yours, Mike.
> 
> Strategist - Emerging Technologies, SCA & SDO.
> Co Chair OASIS SCA Assembly TC.
> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
> Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
> Email: mike_edwards@uk.ibm.com
> 
> From:                
 Raymond Feng <rfeng@us.ibm.com>
> To:                
 sca-assembly@lists.oasis-open.org
> Date:                
 03/08/2009 22:24
> Subject:              
   [sca-assembly] A few questions on the SCA proprty
values
> 
> 
> ------------------------------------------------------------------------
> 
> 
> 
> Hi,
> 
> I have a few questions on the SCA property values.
> 
> 1. Is a) a valid property definition in the composite file? If I 
> understand the text in Assembly spec line 991 (As a value, supplied
as 
> the content of the property element.), it should be valid.
> 
> a) <property name="prop1" type="xsd:string">ABC</property>
> *
> <mje>Yes, this is valid. It was discussed in a recent Assembly
meeting 
> when considering a related Issue resolution</mje>*
> 
> Please note that prop1 is a string property and the value "ABC"
is the 
> direct text under <property>. I understand that it can be expressed
in 
> two other variants:
> 
> b) <property name="prop1" type="xsd:string"
value="ABC"/>
> c) <property name="prop1" type="xsd:string">
> <value>ANC</value>
> </property>
> *
> <mje>Yes, these are valid</mje>*
> 
> 3. If the property value is specified using @file, for example,
> 
> <property name="prop1" file="prop1.txt"/>
> 
> How should the content of "prop1.txt" be used? As the textural
inclusion 
> or XML inclusion? Please note if the "prop1" can have many
values 
> (@many="true"), we need to define multiple instances of
the property 
> value in "prop1.txt". In such cases, the content cannot
be a well-formed 
> XML document as there is no single root element.
> *
> <mje>It is textural inclusion, but the spec does not say so,
and so the 
> spec could well do with clarification</mje>*
> 
> Two examples are listed below:
> 
> a) Single value:
> <value 
> xmlns="_http://docs.oasis-open.org/ns/opencsa/sca/200903_">ABC</value>
> 
> b) Multiple values:
> <value xmlns="_http://docs.oasis-open.org/ns/opencsa/sca/200903_">1</value>
> <value xmlns="_http://docs.oasis-open.org/ns/opencsa/sca/200903_">2</value>
> *
> <mje>These are valid</mje>*
> 
> Thanks,
> Raymond
> ------------------------------------------------------------------------
> *Raymond Feng*
> Senior Software Engineer, Apache Tuscany PMC Member & Committer
/
> IBM Bay Area Lab, 1001 E Hillsdale Blvd, Suite 400, Foster City, CA
> 94404, USA/*/
> E-mail/*/: //_rfeng@us.ibm.com_/ <mailto:rfeng@us.ibm.com>/,
> /*/Notes/*/: Raymond Feng/Burlingame/IBM, /*/Tel/*/: 650-645-8117,
> /*/T/L/*/: 367-8117/*/
> Apache Tuscany/*/: //_http://tuscany.apache.org_/ 
> <http://tuscany.apache.org/>/
/
> ------------------------------------------------------------------------
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> /
> /
> 
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
number 
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU/
> 
> 
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU