[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Also document properties do not apply to files (digital/hardcopy files)
since they are not subtypes of product & do not have am associated
definition, but cannot use the existing capability because the
property_assignment_select type does not include files. In fact it only
includes one of the 18 possible types, which means potentially another 17
capabilities to cover all!
Documents could be covered by adding one subtype to the existing capability
(assigned_document_property) & adding two items to the above mentioned
select type (since document_definition is not a subtype of
product_view_definition & files are independantly defined).
I can create a new capability or add to existing ones but it would mean
repeating a large amount of information already within
assigning_product_properties.
regards,
Tim
-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 29 July 2004 03:30
To: plcs-dex@lists.oasis-open.org
Subject: [plcs-dex] document properties
Hi
An issue was raised against the capability: Capability (C076):-
assigning_product_properties
that we should include document properties in it.
Given that we decided to treat product properties, resource properties and
activity properties as separate capabilities, and given that the document
property module subtypes the generic property model,
it seems to me that document properties should not be part of
assigning_product_properties
Rather it should either be a separate capability or part of
representing_documents capability.
Given that you nearly always want to represent a documents properties
whenever you represent a document and given that document properties will
never be used with anything other than documents, I think that document
properties should form part of the representing_documents capability
Any thoughts?
Regards
Rob
-------------------------------------------
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401
------=_NextPart_000_0001_01C47F0A.86185A80
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR>
<STYLE>@font-face {
font-family: Verdana;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt =
90.0pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"
}
SPAN.EmailStyle17 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; =
FONT-FAMILY: Arial; TEXT-DECORATION: none
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-GB vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2>Apologies for the late reply Rob,</FONT></SPAN></DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2>From=20
another view, document is a type of product and as such should =
therefore, be=20
handled by this capability rather than creating or enlarging the scope =
of other=20
capabilities that are already becomming too =
large. </FONT></SPAN></DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2>Also document properties do not apply to files =
(digital/hardcopy=20
files) since they are not subtypes of product & do not have am =
associated=20
definition, but cannot use the existing capability because the=20
property_assignment_select type does not include files. In fact it only =
includes=20
one of the 18 possible types, which means potentially another 17 =
capabilities to=20
cover all! </FONT></SPAN></DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2>Documents could be covered by adding one subtype to the =
existing=20
capability (assigned_document_property) & adding two items to =
the above=20
mentioned select type (since document_definition is not a subtype of=20
product_view_definition & files are independantly=20
defined).</FONT></SPAN></DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D014260217-10082004><FONT face=3DArial color=3D#0000ff =
size=3D2>I can=20
create a new capability or add to existing ones but it would mean =
repeating=20
a large amount of information already within=20
assigning_product_properties.</FONT></SPAN></DIV><SPAN=20
class=3D014260217-10082004></SPAN><FONT face=3DTahoma><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><FONT face=3DArial color=3D#0000ff size=3D2></FONT>
<DIV><BR><FONT size=3D2><SPAN class=3D014260217-10082004><FONT =
face=3DArial=20
color=3D#0000ff>regards,</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D014260217-10082004>Tim</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D014260217-10082004></SPAN></FONT> </DIV>
<DIV><FONT size=3D2><SPAN =
class=3D014260217-10082004> </SPAN>-----Original=20
Message-----<BR><B>From:</B> Rob Bodington=20
[mailto:rob.bodington@eurostep.com]<BR><B>Sent:</B> 29 July 2004=20
03:30<BR><B>To:</B> plcs-dex@lists.oasis-open.org<BR><B>Subject:</B> =
[plcs-dex]=20
document properties<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Hi</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">An issue was raised =
against the=20
capability: </SPAN></FONT><B><FONT face=3DVerdana size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9.5pt; FONT-FAMILY: =
Verdana">Capability=20
(C076):— assigning_product_properties</SPAN></FONT></B></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">that we should include =
document=20
properties in it.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Given that we decided to =
treat=20
product properties, resource properties and activity properties as =
separate=20
capabilities, and given that the document property module subtypes the =
generic=20
property model, </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">it seems to me that =
document=20
properties should not be part of=20
assigning_product_properties</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Rather it should either =
be a=20
separate capability or part of representing_documents=20
capability.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Given that you nearly =
always want=20
to represent a documents properties whenever you represent a document =
and=20
given that document properties will never be used with anything other =
than=20
documents, I think that document properties should form part of the=20
representing_documents capability</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Any =
thoughts?</SPAN></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards<BR>Rob</SPAN></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">------------------------------------------- <BR><=
/SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Rob=20
Bodington</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><BR>Eurostep =
Limited<BR>Web Page:=20
</SPAN></FONT><A href=3D"http://www.eurostep.com";><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">http://www.eurostep.com</SPAN></FONT></A><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">=20
</SPAN></FONT><A href=3D"http://www.share-a-space.com";><FONT =
face=3DArial=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">http://www.share-a-space.com</SPAN></FONT></A><BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Email:=20
Rob.Bodington@eurostep.com<BR>Phone: +44 (0)1454 =
270030<BR></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Mobile</SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">: +44=20
(0)7796 176 401</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"></SPAN></FONT> </P></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0001_01C47F0A.86185A80--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]