Rules for specifying URI for artifact types and attributes
The rules for cross project copying state that source and destination types must have the same RDF URI, and the same attribute sets.
None of our types or attributes have the URI set. What constraints are there on entering a valid URI?
Does the root value need to match an existing valid address? Or can I just do "HTML://xxx.com/attribute/Status"?
The documentation is not very clear on this.
Thomas
None of our types or attributes have the URI set. What constraints are there on entering a valid URI?
Does the root value need to match an existing valid address? Or can I just do "HTML://xxx.com/attribute/Status"?
The documentation is not very clear on this.
Thomas
Accepted answer
The strategic reuse guidance on jazz.net has recently been updated and includes some user-focused (as opposed to reference) material on this. Take a look starting here. There is no requirement for the URI to refer to a valid address, though it might make sense as a way to avoid potential future issues. Hope this helps.