Issue 7828: PDTnet Queries Conformance Point                                                                                                                                                                        (plm-ftf)
Source: Zentrum fuer Graphische Datenverarbeitung e.V. (Mr. Steffen Nowacki, steffen.nowacki@partmaster.de)
Nature: Uncategorized Issue
Severity: 
Summary: The Queries defined in the PDTnet Queries Conformance Point
do not match the Use Cases defined in Chapter 2.2 but are only
specific Queries which can be used as building blocks to define
Queries that fulfill the requirements of the Use Cases.


So this Conformance Point should be renamed in
"Specific Queries Conformance Point" and a new Conformance Point
should be added to the Specification which define the Queries,
which fulfill exactly the requirements of  the use cases.


Resolution: 
Revised Text: Resolution:
The existing conformance point "PDTnet Queries Conformance Point" is renamed to "Specific Queries Conformance Point" and a new conformance point "PDTnet Queries Conformance Point" with ten queries is introduced.
For the definitions of the semantics of the new queries one new construct "Conditional_query" (see merged issue 8584) and one new specific_query "Assembly_component_placement_query" (see resolution to issue 8585) are needed, and are defined too.
Revised Text
Change single sentence paragraphin section 8.9 as follows:
The Query type provides the possibility of concatenated conditional, and recursive queries, respectively.
Append at the end of section 8.9

 
Figure 0 10 Class diagram of class Conditional_query
The type Conditional_query enables the execution of a query in dependency of a condition. If the attributes evaluates true, the query referenced by query is executed otherwise the query is not executed. 

Insert new complexType "Conditional_query" in PLMComputationalModel.xsd

			<xs:complexType name="Conditional_query"> 
				<xs:complexContent> 
					<xs:extension base="Query"> 
						<xs:sequence> 
							<xs:element name="Attribute_is_true" type="xs:boolean" minOccurs="0"/> 
							<xs:element name="Attribute_is_not_true" type="xs:boolean" minOccurs="0"/> 
							<xs:element name="Attribute_is_set" type="xs:string" minOccurs="0"/> 
							<xs:element name="Attribute_is_not_set" type="xs:string" minOccurs="0"/> 
							<xs:element name="Query" type="Query"/> 
						</xs:sequence> 
					</xs:extension> 
				</xs:complexContent> 
			</xs:complexType> 

Rename section 8.12 from "PDTnet Queries Conformance Point" to
"Specific Queries Conformance Point" 
Replace first paragraph in section 8.12 by the following text:

The Specific Queries Conformance Point defines a set of low level specialized queries. The semantics of each specialized query of this conformance point is defined by an equivalent Location_path instance. The semantics of Location_path is defined in the Generic Queries Conformance Point.

Insert the following text as new section 8.14

8.14. PDTnet Queries Conformance Point
The PDTnet Queries Conformance Point defines a set of high level specialized queries that fulfill the requirements of the use cases described in section /CROSSREF 7.2. The semantics of each specialized query of this conformance point is defined by an equivalent Query instance from the Specific Queries Conformance Point.
 
8.14.1 General_detail_query
The General_detail_query returns general detail information from objects selected by a uid.
Parameters:
·	uids : UID[0..*]
·	relating_type_name : String [0..*]
·	add_aliases : Boolean [0..1]
·	alias_id : String [0..1]
·	add_authorizations : Boolean [0..1]
·	authorization_role : String [0..1]
·	add_dates : Boolean [0..1]
·	date_role : String [0..1]
·	add_properties : Boolean [0..1]
·	property_name : String [0..1]
·	add_classifications : Boolean [0..1]
·	classification_role : String [0..1]
·	add_approvals : Boolean [0..1]
·	approval_level : String [0..1]
·	add_activities : Boolean [0..1]
·	activity_role : String [0..1]
·	add_effectivities : Boolean [0..1]
·	effectivity_role : String [0..1]
 
Figure 0 11 Definition, sample instance and equivalent specific query instance of the General_detail_query
8.14.2 Document_detail_query
The Document_detail_query returns detail information of an Document, Document_version, or Document_representation object selected by a uid.
Parameters (without inherited):
·	classification_name : String [0..1]
·	add_versions : Boolean [0..1]
·	version_id : String [0..1]
·	add_representations : Boolean [0..1]
 
Figure 0 12 Definition, sample instance and equivalent specific query instance of the Document_detail_query
8.14.3 Document_selection_query
The Document_selection_query selects objects of class Document and includes related Document_version and Document_representation objects.
Parameters:
·	name : String [0..1]
·	id : String [0..1]
·	version_id : String [0..1]
·	classification_name : String [0..1]
 
Figure 0 13 Definition, sample instance and equivalent specific query instance of the Document_selection_query
8.14.4 Document_ traversal_query
The Document_traversal_query traverses from a Document_representation object selected by its uid via Document_structure objects to related Document_representation objects in a document structure.
Parameters:
·	uid : UID
·	maximum_recursion_number : Integer [0..1]
·	relation_type : String [0..1]
 
Figure 0 14 Definition, sample instance and equivalent specific query instance of the Document_traversal_query
8.14.5 Item_detail_query
The Item_detail_query returns detail information of an Item, Item_version, Design_discipline_item_definition, Item_instance or Assembly_component_relationship object selected by a uid.
Parameters (without inherited):
·	add_version_relationships : Boolean [0..1]
·	version_relationship_type : String [0..1]
·	add_documents : Boolean [0..1]
·	document_role : String [0..1]
·	classification_name : String [0..1]
·	add_placement : Boolean [0..1]
 
Figure 0 15 Definition, sample instance and equivalent specific query instance of the Item_detail_query
8.14.6 Item_selection_query
The Item_selection_query selects objects of class Item and includes related Item_version and Design_discipline_item_definition objects.
Parameters:
·	name : String [0..1]
·	id : String [0..1]
·	version_id : String [0..1]
·	classification_name : String [0..1]
 
Figure 0 16 Definition, sample instance and equivalent specific query instance of the Item_selection_query
8.14.7 Item_ traversal_query
The Item_traversal_query traverses from a Design_discipline_item_definition object to the higher or lower Design_discipline_item_definition objects in an assembly structure.
Parameters:
·	uid : UID
·	maximum_recursion_number : Integer [0..1]
·	inverse_direction : Boolean [0..1]
 
Figure 0 17 Definition, sample instance and equivalent specific query instance of the Item_traversal_query
8.14.8 Product_ detail_query
The Product_detail_query returns detail information of an Complex_product object selected by a uid.
Parameters (without inherited):
·	add_configurations : Boolean [0..1]
·	configuration_type : String [0..1]
·	add_documents : Boolean [0..1]
·	document_role : String [0..1]
 
Figure 0 18 Definition, sample instance and equivalent specific query instance of the Product_detail_query

8.14.9 Product_ selection_query
The Product_selection_query selects objects of class Product_class and includes Product_function_component_select related via Class_structure_relationship objects.
Parameters:
·	name : String [0..1]
·	id : String [0..1]
 
Figure 0 19 Definition, sample instance and equivalent specific query instance of the Product_selection_query
8.14.10 Product_traversal_query
The Product_traversal_query traverses from a Complex_product object selected by its uid via Product_structure_relationship or Alternative_solution_objects to related Complex_product or Item_instance objects in a product structure.
Parameters:
·	uid : UID
·	maximum_recursion_number : Integer [0..1]
·	relation_type : String [0..1]
 
Figure 0 20 Definition, sample instance and equivalent specific query instance of the Product_traversal_query
Insert include statement in WSDL

	<wsdl:import namespace="http://www.omg.org/PLMServices1.1/PdtnetQueries" 
		location="http://schema.omg.org/plm/1.1/PdtnetQueries.xsd"/>
 

Add new Document "PdtnetQueries.xsd" as normative Document to the specification

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema targetNamespace="http://www.omg.org/PLMServices1.1/PdtnetQueries" 
	xmlns:xs="http://www.w3.org/2001/XMLSchema" 
	xmlns:plm-cm="http://www.omg.org/PLMServices1.1/ComputationalModel">
  	xmlns="http://www.omg.org/PLMServices1.1/PdtnetQueries">
  
  <xs:import namespace="http://www.omg.org/PLMServices1.1/ComputationalModel" 
  	schemaLocation="http://schema.omg.org/plm/1.1/PLMComputationalModel.xsd"/>
  
  <xs:complexType name="General_detail_query">
    <xs:complexContent>
      <xs:extension base="plm-cm:Query">
        <xs:sequence>
          <xs:element name="uids" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
          <xs:element name="Relating_type_name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
          <xs:element name="Add_aliases" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Alias_id" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_authorizations" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Authorization_role" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_dates" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Date_role" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_properties" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Property_name" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_classifications" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Classification_role" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_approvals" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Approval_level" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_activities" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Activity_role" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_effectivities" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Effectivity_role" type="xs:string" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>

  <xs:complexType name="Document_detail_query">
    <xs:complexContent>
      <xs:extension base="General_detail_query">
        <xs:sequence>
          <xs:element name="Classification_name" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_versions" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Version_id" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_representations" type="xs:boolean" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
    
  <xs:complexType name="Document_selection_query">
    <xs:complexContent>
      <xs:extension base="plm-cm:Query">
        <xs:sequence>
          <xs:element name="Name" type="xs:string" minOccurs="0"/>
          <xs:element name="Id" type="xs:string" minOccurs="0"/>
          <xs:element name="Version_id" type="xs:string" minOccurs="0"/>
          <xs:element name="Classification_name" type="xs:string" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
  
  <xs:complexType name="Document_traversal_query">
    <xs:complexContent>
      <xs:extension base="plm-cm:Query">
        <xs:sequence>
          <xs:element name="uid" type="xs:string"/>
          <xs:element name="Relation_type" type="xs:string" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>

  <xs:complexType name="Item_detail_query">
    <xs:complexContent>
      <xs:extension base="General_detail_query">
        <xs:sequence>
          <xs:element name="Classification_name" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_documents" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Document_role" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_version_relationships" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Version_relationship_type" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_placements" type="xs:boolean" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
    
  <xs:complexType name="Item_selection_query">
    <xs:complexContent>
      <xs:extension base="plm-cm:Query">
        <xs:sequence>
          <xs:element name="Name" type="xs:string" minOccurs="0"/>
          <xs:element name="Id" type="xs:string" minOccurs="0"/>
          <xs:element name="Version_id" type="xs:string" minOccurs="0"/>
          <xs:element name="Classification_name" type="xs:string" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
  
  <xs:complexType name="Item_traversal_query">
    <xs:complexContent>
      <xs:extension base="plm-cm:Query">
        <xs:sequence>
          <xs:element name="uid" type="xs:string"/>
          <xs:element name="Inverse_direction" type="xs:boolean" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>

  <xs:complexType name="Product_detail_query">
    <xs:complexContent>
      <xs:extension base="General_detail_query">
        <xs:sequence>
          <xs:element name="Classification_name" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_documents" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Document_role" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_version_relationships" type="xs:boolean" minOccurs="0"/>
          <xs:element name="Version_relationship_type" type="xs:string" minOccurs="0"/>
          <xs:element name="Add_placements" type="xs:boolean" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
    
  <xs:complexType name="Product_selection_query">
    <xs:complexContent>
      <xs:extension base="plm-cm:Query">
        <xs:sequence>
          <xs:element name="Name" type="xs:string" minOccurs="0"/>
          <xs:element name="Id" type="xs:string" minOccurs="0"/>
          <xs:element name="Version_id" type="xs:string" minOccurs="0"/>
          <xs:element name="Classification_name" type="xs:string" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
  
  <xs:complexType name="Product_traversal_query">
    <xs:complexContent>
      <xs:extension base="plm-cm:Query">
        <xs:sequence>
          <xs:element name="uid" type="xs:string"/>
          <xs:element name="Inverse_direction" type="xs:boolean" minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>

</xs:schema>

Actions taken:
October 1, 2004: received issue
August 1, 2005: closed issue
Discussion: 

End of Annotations:=====
te: Fri, 01 Oct 2004 11:31:16 +0200 
From: Steffen Nowacki <steffen.nowacki@partmaster.de> 
User-Agent: Thunderbird 0.6 (Windows/20040502) 
X-Accept-Language: de-de, de-at, de, en-us, en 
To: issues@omg.org 
Subject: issue for PLM Services 1.0 


PLM Services 1.0
Document mantis/04-04-01
Revision Date 05/05/2004
Chapter 3.11
Page: 362


PDTnet Queries Conformance Point


The Queries defined in the PDTnet Queries Conformance Point
do not match the Use Cases defined in Chapter 2.2 but are only
specific Queries which can be used as building blocks to define
Queries that fulfill the requirements of the Use Cases.


So this Conformance Point should be renamed in
"Specific Queries Conformance Point" and a new Conformance Point
should be added to the Specification which define the Queries,
which fulfill exactly the requirements of  the use cases.


Steffen Nowacki


Date: Mon, 21 Mar 2005 09:10:15 +0100 
From: Steffen Nowacki <steffen.nowacki@partmaster.de> 
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) 
X-Accept-Language: de-DE, de, en-us, en 
To: "Lämmer, Lutz (PROSTEP)" <laemmer@prostep.com> 
Cc: plm-ftf@omg.org 
Subject: plm services issue 7828 


Hallo Lutz,


the proposed solution of issue 7828 needs a revision.


The insertion of the Assenbly_component_query can  be removed because  it is already  introduced as solution  of issue  8585.


The definition of the General_detail_query uses the Associated_effectivity_query,
which is not yet defined in the specific queries conformance point.


Best regards,
Steffen.


-- 
PartMaster GmbH              E-Mail: steffen.nowacki@partmaster.de
Lagerstrasse 44/45           WWW   : http://www.partmaster.de
D-18055 Rostock, Germany     Phone : +49 381 20373996
                            Fax   : +49 381 20373994





PartMaster GmbH