3.5.3 The metaIdRef attribute

[sbmlsecretary]

The paragraph starting at page 8, line 4 "Note that..." is not clear to me. Of course, referenced objects must be normal model components. What is the problem here being addressed?

Reported by: andreas-draeger

Original Ticket: sbml/sbml-specifications//308

[sbmlsecretary]

With hierarchy, there can be other Model objects in the same document, and since metaIDs must be unique across the whole document, you could theoretically have cross-Model references with a metaIdRef attribute. We are explicitly calling this out as illegal here.

Original comment by: luciansmith

[sbmlsecretary]

Ok, now it makes sense. Thanks for clarifying.

Original comment by: andreas-draeger

[sbmlsecretary]

Do you think the specification also needs some sort of clarification, or do you think it's OK?

Original comment by: luciansmith

[sbmlsecretary]

Maybe it would be slightly better to write it like this:

Note that even if used in conjunction with the HierarchicalModel Composition package, this attribute is not allowed to reference elements from that reside within other Model objects in the same SBML Document. Referenced elements must be normal members of the parent Model containing the Member object, and submodel elements may be normally accessed by creating replacements.

Original comment by: andreas-draeger

[sbmlsecretary]

• status: open --> pending
• Group: Reported-Proposed --> Accept-no-conformance-implications

Original comment by: luciansmith

[sbmlsecretary]

Done! This change is now incorporated into SVN, and will be part of the forthcoming release candidate.

Original comment by: luciansmith

[sbmlsecretary]

• status: pending --> closed

Original comment by: luciansmith