<div dir="ltr">Hi all,<div><br></div><div>to be fair, the replies have been thoroughly revised with the chairs, and with the inputs from various authors I contacted for validation. The changes are restricted to typos and obvious inconsistencies, to keep the direction agreed on at the Paris interop meeting.</div><div><br></div><div>Here is the list of changes in the text:</div><div>* "Boisson" before "Bonnarel" in author list (alphabetical order)<br>* removed "not-null" hint from EntityDescription Table 12<br>* EntityDescription (2.5.3): "must" replaced by "are expected to"<br>* add for Descriptions classes (2.5): "If an instance of Used/WasGeneratedBy/Entity is linked to its corresponding description, then there must exist a link between the corresponding activity and activity description."<br>* Figure 7: "bound to" replaced by "bound with"<br>* Agent (2.4.1): "with a different role" removed<br>* artefactType attribute (Table 23): data type changed from string to TypeOfConfigArtefact (string restricted to "Parameter" or "ConfigFile" values)<br>* ParameterDescription.default (Table 20): "entity" replaced by "parameter"<br>* unit attributes (Tables 18 and 20): changed data type string to Unit in tables 18 and 20 with a reference to C.1.1.<br>* comments in Table 9 now start with lower case (no capitals)<br>* changed "main" to "Main" for usage/generation type in text (2.5.4)<br>* multiplicity attributes (Tables 13 and 14) are of data type string, "*" replaced by "unbounded"<br>* Makefile typo (texi --> tex)<br>* some classes were missing the \class{} format<br>* add photographic plates as example of entities (sections 1 and 2.2.1)<br>* invalidatedAtTime attribute (Table 1): "This does not relate to the validity of the entity." removed<br>* the UML model has been re-done from scratch to get rid of corrupted data. We have new diagrams with much comments and descriptions to come within the VODML file.<br>* Person (Table 6): replace by "person agents are people, e.g. described by their name or their official position"<br>* Organization (Table 6): replace by "an organization is a social or legal institution, e.g. an institute, a consortium, a project"<br>* Specific types of entities (2.6): add "The entity description classes for both ValueEntity and DatasetEntity are subsetted respectively as ValueDescription or DatasetDescription."<br>* DatasetDescription (2.6.1): "file" replaced by "dataset", "may" removed<br>* rephrase meaning of colors in modeling conventions<br>* text for multiplicity (2.5.3): add "for a given ActivityDescription instance"<br>* ActivityConfiguration (2.7): "connected with" replaced by "connecting ... with the Activity class"<br></div><div><br></div><div>Best regards,</div><div>Mathieu</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 17 juil. 2019 à 16:25, Laurent Michel <<a href="mailto:laurent.michel@astro.unistra.fr">laurent.michel@astro.unistra.fr</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">(sorry if you got this message twice)<br>
<br>
Dear DMers ,<br>
<br>
The WD period is over and it is time to move on.<br>
The development process of this standard is a long trip and I would like to thank all of the contributors, the whole WG as well <br>
as the TCG for this achievement.<br>
There were lots of change requests which have all been taken into account by M. Servillat, the document editor.<br>
All of these requests are listed below with the editor answers.<br>
We need now a couple of days to arrange the PR2 page and to publish all that material on ivoadoc.<br>
You will be notified when the PR stage will start.<br>
<br>
Best<br>
<br>
LM<br>
<br>
Editor Answers<br>
=============<br>
1. Prov-WD: Prov-WD: small authors list problem<br>
* ok, Boisson before Bonnarel (editors, including former editors, then alphabetical list)<br>
2. Prov-WD: "package" unexplained in modeling_conventions.tex<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005855.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005855.html</a><br>
* We are not redefining every UML feature in the modeling conventions, this addition brings nothing and is thus not necessary<br>
3. Prov-WD: Remove "not-null" hint from EntityDescription table<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005853.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005853.html</a><br>
* ok<br>
4. Prov-WD: Cleanup from unused text<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005857.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005857.html</a><br>
* This has no impact on the generated PDF, and it is at the editor's discretion<br>
5. Prov-WD: Remove unused color definitions<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005856.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005856.html</a><br>
* This has no impact on the generated PDF, and it is at the editor's discretion<br>
6. Prov-WD: ProvTAP vs. Provenance data model review<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005852.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005852.html</a><br>
* out of topic, ProvTAP is a different standard than the data model, still in development. The scope of ProvTAP will be <br>
defined later, and it may or may not bring some restrictions with respect to the data model.<br>
7. Prov-WD: Attribute missing in Figure 7<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005854.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005854.html</a><br>
* Modelio models were updated (the issue here was the size of the box)<br>
8. Prov-WD: Wrong multiplicity of Activity --> WasConfiguredBy<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005858.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005858.html</a><br>
* The relation multiplicities in Fig 1, 7 and 8 are: "Activity 1 --> * WasConfiguredBy" as they should indeed be. This was <br>
checked in the latest figures.<br>
9. Prov-WD: W3C compatibility review<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005859.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005859.html</a><br>
* W3C compatibility is not a requirement. The requirement is "Provenance information should be serializable into the W3C <br>
provenance standard formats (PROV-N, PROV-XML, PROV-JSON) with minimum information loss."<br>
* This will be investigated for the serialization specification, not in the data model document, which already ensures that <br>
the core model is fully based on W3C concepts (so the requirement at this level is met).<br>
10. Prov-WD: Usage/GenerationDescription -> EntityDescription relation<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005860.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005860.html</a><br>
* There is no restriction as descriptions are optional (multiplicity 0..1), but to avoid confusion, "must" is now replaced <br>
by "if ... is expected to" in the examples (as this is in another context than the definition of the standard)<br>
* An additional clarification is needed to indicate that the relation Activity-ActivityDescription is dominant: "If an <br>
instance of Used/WGB/ED is linked to its corresponding description, then there must exist a link between the corresponding <br>
activity and activity description."<br>
* MAY is properly given (2.5.3) : "Instances of Used (respectively WasGeneratedBy) may thus point to an instance of <br>
UsageDescription (respectively GenerationDescription)."<br>
* In 2.7.1, it is properly explained that "The corresponding description classes, ParameterDescription and <br>
ConfigFileDescription, are both defined in the context of the description of an activity"<br>
11. Prov-WD: Figure 7: relations are mentioned in the wrong direction<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005861.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005861.html</a><br>
* changed to "bound with", no direction is involved.<br>
12. Prov-WD: Several Agents may have the same role<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005862.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005862.html</a><br>
* this is just an illustration, but "with a different role" is removed to avoid confusion<br>
13. Prov-WD: Multiplicity of Entity->WasGeneratedBy is wrong<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005863.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005863.html</a><br>
* In all figures, the relation is "Entity 1 --> 0..1 WasGeneratedBy" as it should indeed be. This was checked in the latest <br>
figures.<br>
14. Prov-WD: wasConfiguredBy.artefactType has the wrong type<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005864.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005864.html</a><br>
* ok, the text will indicates: "artefactType, TypeOfConfigArtefact, string that takes the value "Parameter" or "ConfigFile" <br>
to indicate the type of class pointed by the WasConfiguredBy instance."<br>
15. Prov-WD: Wrong description of ParameterDescription.default<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005865.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005865.html</a><br>
* indeed, "entity" has to be replaced by "parameter" here.<br>
16. Prov-WD: Agent type list differs from the one in the table<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005866.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005866.html</a><br>
* The table indicates the precise "Enumeration of Agent types", while the text illustrates this ("can").<br>
* + "for instance"<br>
17. Prov-WD: Type mismatch for "unit" between text and figures<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005867.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005867.html</a><br>
* unit is a string that follows a recommended form.<br>
* changed to Unit in the table with a reference to C.1.1.<br>
18. Prov-WD: Harmonize name of descriptive column and lowercase first char in table<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005868.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005868.html</a><br>
* the comments in Table 9 were changed to lower case only.<br>
19. Prov-WD: ValueEntityDescription: "default" attribute has unclear description<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005869.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005869.html</a><br>
* It seems clear that ValueEntityDescription.default is the default value in the context of the activity description (i.e. <br>
the expected default value). It may then be compared to ValueEntity.value to check if the default was used or not.<br>
20. Prov-WD: capitalize "main" use/generation type in text<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005870.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005870.html</a><br>
* ok<br>
21. Prov-WD: "multiplicity" attributes in Usage/GenerationDescription unclear<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-June/005871.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-June/005871.html</a><br>
* the data type is string, and it contains a number or a word to indicate that the value is unbounded.<br>
* "*" is replaced by "unbounded" which is commonly used (minOccur, maxOccur in XSD)<br>
22. Prov-WD: Document should be accessible<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005872.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005872.html</a><br>
* The descriptions of relations was discussed within the group.<br>
23. Prov-WD: Misleading reproducibility phrasing<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005873.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005873.html</a><br>
* the replacement proposed does not bring more information, so we should keep the text agreed at the Paris interop meeting.<br>
24. Prov-WD: open publishing policy for science data not referenced<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005874.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005874.html</a><br>
* this sentence references the FAIR principles that are explicitly about "simple guideposts to inform those who publish", <br>
and there is no question that "open publishing" (<a href="https://en.wikipedia.org/wiki/Open_publishing" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Open_publishing</a>) is relevant to science data, and <br>
largely adopted in astronomy.<br>
25. Prov-WD: Secondary, unneeded/irritating definition of provenance<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005875.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005875.html</a><br>
* this overview was requested in the first RFC, it provides an accessible description (not a definition) of the concepts <br>
manipulated.<br>
* + "In the VO context, ... is thus..."<br>
26. Prov-WD: Fix typo in Makefile<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005879.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005879.html</a><br>
* ok<br>
27. Prov-WD: Activity, Entity, ActivityConfiguration not formatted<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005880.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005880.html</a><br>
* ok<br>
28. Prov-WD: Wrong object in agent role descriptions<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005886.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005886.html</a><br>
* maybe "Author" is more relevant for an entity, and "Operator" more relevant for an activity, but there is no strict rule <br>
(see W3C PROV examples). The list simply reflects what is found in astronomy projects in general.<br>
29. Prov-WD: Use Plates as example for Entity<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005885.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005885.html</a><br>
* ok<br>
30. Prov-WD: Make clear that ConfigFiles are not entities<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005886.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005886.html</a><br>
* ConfigFile is not linked to Entity in the model, this is clear.<br>
31. Prov-WD: Use versionized URLs for W3C standards<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005889.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005889.html</a><br>
* ok<br>
32. Provenance DM WD review - invalidatedAtTime description<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005890.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005890.html</a><br>
* Removed misleading sentence: "This does not relate to the validity of the entity."<br>
33. Prov-WD: AgentType descriptions confusing<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005899.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005899.html</a><br>
* ok to take the W3C definition, plus our examples<br>
* + Person: Person agents are people, e.g. described by their name or their position<br>
* + Organization: an organization is a social or legal institution, e.g. an institute, a consortium, a project<br>
34. Prov-WD: Separation of possible values in ParameterDescription.options and ValueDescription.options<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005900.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005900.html</a><br>
* as values are represented by a string, it is straightforward to have options as a comma separated values, as agreed at <br>
the Paris meeting<br>
35. Prov-WD: Restrictions for specific Entities not formulated<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005903.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005903.html</a><br>
* "The entity description classes for both ValueEntity and DatasetEntity are subsetted respectively as ValueDescription or <br>
DatasetDescription."<br>
36. Prov-WD: DatasetEntity not clearly defined<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005904.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005904.html</a><br>
* the defined structure of a dataset is given by the contentType, this gives freedom to manpulate any dataset a project <br>
wants to define<br>
37. Prov-WD: Conflicting description of DatasetDescription.contentType<br>
* <a href="http://mail.ivoa.net/pipermail/dm/2019-July/005905.html" rel="noreferrer" target="_blank">http://mail.ivoa.net/pipermail/dm/2019-July/005905.html</a><br>
* indeed, "file" is better replaced by "dataset"<br>
* it is better to remove "may", as the objective is to illustrate<br>
<br>
<br>
<br>
-- <br>
jesuischarlie/Tunis/Paris/Bruxelles/Berlin<br>
<br>
Laurent Michel<br>
SSC XMM-Newton<br>
Tél : +33 (0)3 68 85 24 37<br>
Fax : +33 (0)3 )3 68 85 24 32<br>
Université de Strasbourg <<a href="http://www.unistra.fr" rel="noreferrer" target="_blank">http://www.unistra.fr</a>><br>
Observatoire Astronomique<br>
11 Rue de l'Université<br>
F - 67200 Strasbourg<br>
<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr">Dr. Mathieu Servillat<div>Laboratoire Univers et Théories, Bât 18, Bur. 222</div><div>Observatoire de Paris, Site de Meudon<br><div>5 place Jules Janssen</div><div>92195 Meudon, France</div><div style="font-family:arial,sans-serif;font-size:12.8px;letter-spacing:0.2px">Tél. +33 1 45 07 78 62<br></div><div>--<br></div></div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div>