compared with
Current by Vladimir Alexiev
on Aug 30, 2012 11:42.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (5)

View Page History
This comment was not solicited, it was given on an unrelated topic, so I guess these concerns are not new to Martin :-)

h21. Possible solutions
The complications illustrated above suggest that we need to step on a more specific data model. Below we describe some options

h32. Use a XSD schema
(Vlado) use a more concrete XSD schema or ontology such as [LIDO]
(Dominic) Use LIDO for data representation (of search results) and for data entry purposes.
In this system different object/content types would be defined with a core set of fields derived from the LIDO specification. Specialisation could be added to a seperate catagory and/or project could configure the default representations/data entry forms to conform to their projects particular requirement. This could be linked to a more detailed CRM representation which could also try to represent and 'object' or could be dependent where the user jumped to the CRM representation from the LIDO screen. The CRM view could be more of a browing interface allwing users to explore aspects of the object and jump back into full LIDO representations from a particular point of the CRM browse.

h32. Interlink Simpler Schema or Ontology
(Mariana) Although more complex, CIDOC-CRM gives more expressive power, and there is a lot of support around it, including a large international community. As a compromise we can use the approach of *reference layers* and interlink LIDO with CIDOC-CRM and thus allow flexible usage of the two schemata.
The FRs for [CRM Search] are all based on CIDOC-CRM, so if we are to consider implementing FRs we better have representations with CIDOC-CRM.
Mitac was thinking along the lines of an [Entity API]

h32. "Macros"
(Mike Selway) Delineate parts of the graph using some sort of "macro" approach.
But how to recognize the "macro regions"?

h32. Limited Editing. Structure Comes from XML
(Vlado) RS3 may provide editing only of atomic values, but no reconfiguration of the RDF graph.
Whether this limitation can work should be confirmed by use case elaboration.