Tracker: PLCS PSMmodel

[Index] [All issues]

Id Category Summary Details Priority Status Resolution Release Submitter Assignee Closer
3555619 PLCS PSM XSD No namespace defined? The XSD should define a target namespace : proposal: http://docs.oasis-open.org/ns/plcs/plcsPsm 6 Open Remind phoubaux nobody nobody
3558882 PLCS PSM Model StateAssignmentSelect does not include DocumentDefinition The current capability allows us to identify states for Digital and Physical document definitions but not the more general DocumentDefinition. Since DocumentDefinition is an instantiable supertype of PhysicalDocumentDefinition and DigitalDocumentDefinition I would sugesst removing these two and adding DocumentDefinition. 4 Open Remind philsp nobody nobody
3558997 PLCS PSM Model Allowable units on propertydefinition It is possible to assign a property definition to a part with no value. This is used to make statements like .. all part should have these properties defined. For example an OEM could send a list of part numbers to a supplier to design the parts and a set of assigned property definitions that specify teh properties that are to be be provided. It should also be possible to specify the allowable units that are to be used for the properties. This is available in AP242. Add allowedUnits property to ExternalPropertyDefinition 5 Open Remind robbod nobody nobody
3546351 PLCS PSM Model CollectionAssignment.assignedTo It should be possible to assign a Collection to Person. PersonInOrganization, PersonType, OrganizationType There are probably other things that it should be assigned to as well 5 Pending Accepted R2.0 robbod robbod robbod
3547573 PLCS PSM Model WorkRequest: Mandatory versionId ? WorkRequest shouldn't have a mandatory versionId. Actually wondering if it should have versionIds at all. 5 Pending Accepted R2.0 phoubaux robbod robbod
3547589 PLCS PSM Model Extend Select: JustificationAssignmentSelect Add WorkRequest to JustificationAssignmentSelect 5 Pending Accepted R2.0 phoubaux robbod robbod
3554802 PLCS PSM Model TaskElement encapsulation incorrect TaskElement is encapsulated where ever used, this includes TaskElementRelationship which is incorrect. Suggest we apply the same approach as used for PropertyValue encapsulation and explicitly exclude the relationships from the encapsulation rules. 8 Pending Accepted R2.0 philsp robbod robbod
3555611 PLCS PSM Model Element "Classification' should be Root Element The complex type "Identifier" define the "role" attribute as a reference. According to the schematron rule this attribute should point to a Classification. But Classification is not a top root element in the XSD (not in PlcsData). The following serialization is impossible : <PlcsData> <Organization uid="i3"> <Id> <Identifier id="ANORG" idRoleRef="i2"/> </Id> </Organization> <Classification uid="i2" classRef="i1"/> <ExternalOwlClass uid="i1"> <Class>http://docs.oasis-open.org/ns/plcs/oasis-rdl-en#Identification_code</Class> </ExternalOwlClass> </PlcsData> 8 Pending Accepted R2.0 phoubaux robbod robbod