[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Public Comment
Comment from: stephen_green@bristol-city.gov.uk Name: Stephen Green Title: Organization: UBL Small Business Subcommittee Regarding Specification: 2.0.1 the wording (3.8.1) "The Name attribute SHOULD NOT be used, nor is it intended, for referencing, although it may be important to the business analyst." prevents the use of the Name attribute in the way I had hoped - as an alternative to targetNamespace which is too limiting/specific for, say, designation of a subset of a schema as defined either in a Schematron document or as defined for the UBL 1.0 Small Business Subset. (This is with note to the ebBP provision in the Specification element for documents other than W3C XSD schemas, for example, other ISO DSDL scema types or other definitions such as with CAM.) Two solutions might be 1. to reword the rule to say something like "The Name attribute SHOULD NOT be used, nor is it intended, for document-scoped referencing, although it may be important to the business analyst and could be used to provide a reference to an external document specification where targetNamespace, say, might not be appropriate (such as for a subset or a Schematron schema)." or 2. to either, 2.a., change the targetNamespace attribute to ID, say (since not all document specification types use a targetNamespace as the means to identify themselves) or, 2.b., to add ID as an attribute along with targetNamespace I also question the role of Specification/Name and Specification/NameID. Is the latter used to reference this element internally elsewhere in the BPSS definition instance?
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]