...
Introduced Developer role.
Need to revise Document Reference to add URL/URI and Title.
Lock in as oagis.
Search for Document Reference ACC using filter.
Use ACC filter and DEN sorting to open Document Reference.
Click on Revise. Point out that a developer can revised any published CCs on working branch. The developer would take over the ownership.
However, determined that Document Identification Base ACC needs to be revised instead.
Click on Open in new Tab.
Cancel the revision on the Document Reference.
Go back to Document Identification Base ACC to click on Revise.
Click on append Property Last.
Search for the URI BCCP to add. Fill in Definition Source http://www.openapplications.org/oagis/10 and Definition.
Click on append Property Last.
Search for the Title BCCP to add. Fill in Definition Source http://www.openapplications.org/oagis/10 and Definition. Point out that default cardinality is 0..n. If you need to change the max or min, you can do it. Change it to 1. And change to unbounded again demonstrating that you can type in -1 or unbounded.
Open Document Reference again to show that the URI and Title fields are there. Emphasize the use of double quote.
Create Statement Context Base ACC. Set component type to Base. Point out that when Base is selected Abstract is selected by default. There will be a naming rule implemented later.
Set base of Statement Context to Identification.
Add Document Reference to Statement Context. Filter with ASCCP.
Add Contract Reference to Statement Context. Search “Contract Reference”. Show that clicking on the blank space shows the definition. Show that clicking on the name open up the ASCCP in a new tab for detail inspection.
Create Statement Context ACC.
Set based ACC to Statement Context Base ACC.
Invoke Create OAGi Extension.
Create Statement Context ASCCP.
Log in as sermdev in another window.
Create Statement Base ACC. Set based ACC to Identification. Set Component Type to Base.
Append Free Form Text Group.
Append Statement Context ASCCP. Point out that you can use CC created by another user.
Demonstrate moving the association order. Move Statement Context to before Free Form Text Group.
Create Statement. Set based ACC to Statement Base ACC.
Invoke Create OAGi Extension. Walk through the entities got generated. Point out that Extension is not reusable b/c it is a local element. The name is not unique. Only some properties of Extension components can be edited.
End of Demo.
Jim Wilson's notes from watching the recording of the demo Serm Kulvatunyou presented to the Score WG on . Some comments may apply to Ep1 and some may not.
When adding a property to an ACC, how would one know which ACC in a string of base ACCs to use?
<sermReply> Jim Wilson I think there are two aspects relevant to property placement. 1) OAGIS architecture and 2) semantic appropriateness.
#1 is rather straight forward. You put the property in the ACC whose Object Class Term ends with Base to maintain the extension pattern.
#2 comes in to play when the ACC hierarchy goes beyond 2 level as discussed in #1 (e.g., Substance extends Substance Base). One simple question that could help is to ask whether the additional property is applicable to all other derived ACC or whether you ‘want’ that to be the case. Of course the answer may not be that simple. Taking for example, we want Document Reference to have Title and Status. Document Reference ACC hierarchy is Document Reference → Document Reference Base → Document Identification → Document Identification Base. It can be said that Title semantically applies to Document Identification while Status is not. So Title is better be placed in Document Identification Base while Status is better be placed in Document Reference Base. Notice that both of them are put in the Base ACC according to #1.
</sermReply>
Ep2. Create a standard OAGi BOD
...