Commit f1d8f8e1 authored by Stephan Kreutzer's avatar Stephan Kreutzer

Attempt to fix violation of validity.

parent 69a48c01
<?xml version="1.0" encoding="UTF-8"?><graphml xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://graphml.graphdrawing.org/xmlns/1.0/graphml.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sos="http://www.untiednations.com/SOS" xmlns="http://graphml.graphdrawing.org/xmlns"><graph id="SOS" edgedefault="directed"><key id="sos-poi-title" for="node" attr.name="label" attr.type="string"/><key id="sos-poi-text" for="node" attr.name="description" attr.type="string"/><node id="30"><data key="sos-poi-title"><sos:Title>Grid Prototype 1 interface doesn’t allow navigation to groups of POIs other than the current one if they’re not connected</sos:Title></data><data key="sos-poi-text"><sos:Text>The grid interface to navigate/traverse a graph/network doesn’t provide a way to reach from one group of connected POIs to another group of connected POIs if no POIs from the two separate groups share a connection between the groups. The only way to access separate groups is via the fragment identifier if the user knows the ID of a POI of the group, which is very inconvenient and not an interface control.</sos:Text></data></node><node id="1"><data key="sos-poi-title"><sos:Title>The browser is sandboxed</sos:Title></data><data key="sos-poi-text"><sos:Text>Our prototypes are implemented in the browser. The issue is the “Same Origin Policy” and the problem that Cross-Origin Resource Sharing requires the cooperation of remote, external entities in advance.</sos:Text></data></node><node id="2"><data key="sos-poi-title"><sos:Title>Remote code execution</sos:Title></data><data key="sos-poi-text"><sos:Text>The browser executes unchecked code retrieved from remote, external entities. Such code can be malicious. The browser needs to sandbox the execution in order to protect the computer from compromization. Reasons for it are that no software installation is required in advance (dynamic loading and execution on demand), and that the operating systems running the majority of browsers lack the concept of software distribution repositories where code is submitted and checked, as most of the remote code is proprietary, as well as the operating system that supports this model of denying digital freedom to the user, so the code must be obtained from the original author and can’t be fixed (if broken or malicious), to establish and maintain the dependency.</sos:Text></data></node><node id="13"><data key="sos-poi-title"><sos:Title>Manual software installation is inconvenient</sos:Title></data><data key="sos-poi-text"><sos:Text/></data></node><node id="20"><data key="sos-poi-title"><sos:Title>Lock-in dependency on a single online server/domain/storage/service</sos:Title></data><data key="sos-poi-text"><sos:Text/></data></node><node id="3"><data key="sos-poi-title"><sos:Title>Leakage of confidential data</sos:Title></data><data key="sos-poi-text"><sos:Text>If the browser gets and executes unchecked code from various remote, external entities, it could send the confidential data hold by the other code back from where itself came from and leak it.</sos:Text></data></node><node id="4"><data key="sos-poi-title"><sos:Title>Business model of online service dependency</sos:Title></data><data key="sos-poi-text"><sos:Text>Browser vendors tend to be engaged in some form of SaaS online service lock-in dependency business model, so it would harm their business interest if the sandbox wouldn’t enforce the use of these services and instead would allow to make use of local alternatives.</sos:Text></data></node><node id="5"><data key="sos-poi-title"><sos:Title>Limitations for offline use</sos:Title></data><data key="sos-poi-text"><sos:Text>Data can’t be loaded from or stored to the local hard drive. It’s impossible to interoperate with existing other software on the system. It’s impossible to retrieve data from or submit data to a remote server.</sos:Text></data></node><node id="6"><data key="sos-poi-title"><sos:Title>Quasi-reqirement of online use</sos:Title></data><data key="sos-poi-text"><sos:Text>No data exchange can happen conveniently if it isn’t done with the original remote, external server that delivered the web application files. The operator of the server that delivered the web application files will be faced with responsibilities like data protection, preventing data loss, security, quality of service (uptime and providing the service, so if the service is discontinued, people will loose their work), demands of law enforcement, etc. If the user doesn’t have connectivity, some functions won’t work, for example: uploading a file in order to share/publish and then retrieve it again from the original remote server, because local files can’t be added to the local web software.</sos:Text></data></node><node id="7"><data key="sos-poi-title"><sos:Title>No neutral repository</sos:Title></data><data key="sos-poi-text"><sos:Text>The repository for the prototypes and examples is a personal repository that’s attached to skreutzer’s account: https://gitlab.com/skreutzer/sos-experimental</sos:Text></data></node><node id="8"><data key="sos-poi-title"><sos:Title>Bootstrapping</sos:Title></data><data key="sos-poi-text"><sos:Text>No prior discussion, organizational structures or planning, instead: fast prototyping and ad-hoc setup to reduce the costs of potential failure. Adjust dynamically, build for demand, and not find out after a lot of investment that it turns out to be the wrong result. A main concept of Douglas Engelbart, also known from the Agile Movement, also known from the Lean Movement.</sos:Text></data></node><node id="27"><data key="sos-poi-title"><sos:Title>Practical work is difficult and expensive</sos:Title></data><data key="sos-poi-text"><sos:Text>It is very difficult and expensive to influence the manifest design of existing, real systems according to a theoretical plan. Costs can be time, health, timing/opportunity, enjoyment, mental capacity, etc.</sos:Text></data></node><node id="9"><data key="sos-poi-title"><sos:Title>Bad for linking</sos:Title></data><data key="sos-poi-text"><sos:Text>Links to the repository will lead to skreutzer’s account. A redirect likely can’t be set up later, so moving the repository later likely will break existing links.</sos:Text></data></node><node id="10"><data key="sos-poi-title"><sos:Title>Bad context</sos:Title></data><data key="sos-poi-text"><sos:Text>It’s only a single personal repository on skreutzer’s account, where the context and environment holds many other repositories as well that aren’t related to SOS, so somebody who explores the repository wouldn’t find other SOS material, but unrelated projects, which is bad for the discoverability of the SOS projects. Other SOS repositories aren’t collected in one place, but spread and mixed with other stuff, which is confusing. There is no one-stop-shop authoritative place where all the materials can be found.</sos:Text></data></node><node id="32"><data key="sos-poi-title"><sos:Title>Bad for community management</sos:Title></data><data key="sos-poi-text"><sos:Text>It’s difficult and risky for other people to join and participate, if their contributions are bound to a personal account that’s not related to SOS. Connections might get lost for SOS if a transition needs to happen later.</sos:Text></data></node><node id="33"><data key="sos-poi-title"><sos:Title>Bus factor</sos:Title></data><data key="sos-poi-text"><sos:Text>With git, forking is easy and cheap, so it’s not an effect of too much importance yet that the experimental repository for examples and prototypes is operated by a single person and in case of mishap, malicious actions or loss of availability/interest might become inacessible.</sos:Text></data></node><node id="11"><data key="sos-poi-title"><sos:Title>No connections from SOS</sos:Title></data><data key="sos-poi-text"><sos:Text>There’s no connection from the wcharlton user account nor from the official website http://www.untiednations.com/community/plan-sos/ to the repository, which is bad for discoverability and relies solely on wcharlton’s responsibility to indicate the existence of it, in terms of bus factor.</sos:Text></data></node><node id="12"><data key="sos-poi-title"><sos:Title>Unpublished material</sos:Title></data><data key="sos-poi-text"><sos:Text>Some of William Charlton’s material isn’t published like the grid interface mockup drawings, HTML grid interface mockup, ASPX server prototype, the “SOS - Meeting for Untied Nations/The Ecology of Systems Thinking” and “SOS - Meeting for Cape Town Hackathon” files with their corresponding XSLTs.</sos:Text></data></node><node id="14"><data key="sos-poi-title"><sos:Title>No repository</sos:Title></data><data key="sos-poi-text"><sos:Text>In lack of a shared repository or a personal repository, there is no good place to publish them.</sos:Text></data></node><node id="15"><data key="sos-poi-title"><sos:Title>Copyright</sos:Title></data><data key="sos-poi-text"><sos:Text>For the publication of the material to make sense and be useful, it should be licensed properly. This requires William Charlton to consider the licenses and deciding on one or several of them.</sos:Text></data></node><node id="16"><data key="sos-poi-title"><sos:Title>Incompleteness, not open</sos:Title></data><data key="sos-poi-text"><sos:Text>People who look into the project via the site or the sos-experimental repository won’t be able to get an overview of what has been produced so far. Potential collaborators or independent contributors won’t have access to all the files and might start to waste time by producing similar material which was already produced, but isn’t available.</sos:Text></data></node><node id="17"><data key="sos-poi-title"><sos:Title>No versioning</sos:Title></data><data key="sos-poi-text"><sos:Text>It’s difficult to keep track of the different versions of a file and it can’t easily be established from a given file if it is current or an historic version.</sos:Text></data></node><node id="18"><data key="sos-poi-title"><sos:Title>Backup is difficult</sos:Title></data><data key="sos-poi-text"><sos:Text>It takes a lot of effort to spread the individual files in order to have copies of the whole collection everywhere as a backup mechanism if the original repository or (e-mail) accounts become unavailable.</sos:Text></data></node><node id="19"><data key="sos-poi-title"><sos:Title>SOS formats differ</sos:Title></data><data key="sos-poi-text"><sos:Text>Stephan Kreutzer’s example files differ from William Charlton’s example files. Stephan Kreutzer’s prototypes expect a different format than William Charlton’s prototypes expect. Stephan Kreutzer’s example files don’t validate according to the official XSD.</sos:Text></data></node><node id="21"><data key="sos-poi-title"><sos:Title>Not interoperable</sos:Title></data><data key="sos-poi-text"><sos:Text>Because of differing formats, the prototypes are incompatible and example files are specific to only one of the two prototype groups. The examples can’t be demonstrated to work with all of the prototypes.</sos:Text></data></node><node id="23"><data key="sos-poi-title"><sos:Title>SOS is also a human system tool</sos:Title></data><data key="sos-poi-text"><sos:Text>SOS planning is a method/process/procedure, not just a software tool. It’s intended to be used in specific contexts and setups. The prototypes don’t necessarily reflect the methodological context yet.</sos:Text></data></node><node id="24"><data key="sos-poi-title"><sos:Title>Is pre-existing</sos:Title></data><data key="sos-poi-text"><sos:Text>The Meeting is in William Charlton’s example files and prototypes that pre-existed the creation of the prototypes and examples.</sos:Text></data></node><node id="25"><data key="sos-poi-title"><sos:Title>Meetings not reflected in all examples and prototypes</sos:Title></data><data key="sos-poi-text"><sos:Text>Stephan Kreutzer’s examples and prototypes don’t reflect the concept of the Meeting, which leads to incompatibility with William Charlton’s examples and prototypes that do implement the concept of the Meeting.</sos:Text></data></node><node id="26"><data key="sos-poi-title"><sos:Title>Progress isn’t visible</sos:Title></data><data key="sos-poi-text"><sos:Text>Visitors and potential collaborators/contributors can’t find out about the progress of the project.</sos:Text></data></node><node id="28"><data key="sos-poi-title"><sos:Title>Not very engaging</sos:Title></data><data key="sos-poi-text"><sos:Text>Visitors, potential collaborators and potential contributors might not get attracted because of thinking that the project is inactive.</sos:Text></data></node><node id="29"><data key="sos-poi-title"><sos:Title>No production system</sos:Title></data><data key="sos-poi-text"><sos:Text>The examples and prototypes are somewhat fixed/frozen, they serve as mere examples that shouldn’t be polluted with expansion as a result of real-world usage in order to remain useful and concise, with focus on specific features and characteristics. For the real bootstrapping of this project effort, there’s no production system/environment that also allows organizational enhancements like notifications or versioning to track the history.</sos:Text></data></node><node id="31"><data key="sos-poi-title"><sos:Title>Progress is limited/blocked</sos:Title></data><data key="sos-poi-text"><sos:Text>Bootstrapping can’t improve and advance to a higher stage as the existing results aren’t supposed to and don’t contribute to the actual project effort itself.</sos:Text></data></node><edge id="edge-1" source="8" target="30"/><edge id="edge-2" source="2" target="1"/><edge id="edge-3" source="3" target="1"/><edge id="edge-4" source="4" target="1"/><edge id="edge-5" source="13" target="2"/><edge id="edge-6" source="20" target="2"/><edge id="edge-7" source="20" target="4"/><edge id="edge-8" source="1" target="5"/><edge id="edge-9" source="1" target="6"/><edge id="edge-10" source="8" target="7"/><edge id="edge-11" source="27" target="8"/><edge id="edge-12" source="7" target="9"/><edge id="edge-13" source="7" target="10"/><edge id="edge-14" source="7" target="32"/><edge id="edge-15" source="7" target="33"/><edge id="edge-16" source="7" target="11"/><edge id="edge-17" source="8" target="12"/><edge id="edge-18" source="14" target="12"/><edge id="edge-19" source="15" target="12"/><edge id="edge-20" source="12" target="16"/><edge id="edge-21" source="12" target="17"/><edge id="edge-22" source="12" target="18"/><edge id="edge-23" source="8" target="19"/><edge id="edge-24" source="19" target="21"/><edge id="edge-25" source="25" target="21"/><edge id="edge-26" source="23" target="25"/><edge id="edge-27" source="24" target="25"/><edge id="edge-28" source="8" target="26"/><edge id="edge-29" source="26" target="28"/><edge id="edge-30" source="8" target="29"/><edge id="edge-31" source="29" target="31"/><edge id="edge-32" source="30" target="31"/><edge id="edge-33" source="21" target="31"/></graph></graphml>
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8"?><graphml xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://graphml.graphdrawing.org/xmlns/1.0/graphml.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sos="http://www.untiednations.com/SOS" xmlns="http://graphml.graphdrawing.org/xmlns"><key id="sos-poi-title" for="node" attr.name="label" attr.type="string"/><key id="sos-poi-text" for="node" attr.name="description" attr.type="string"/><graph id="SOS" edgedefault="directed"><node id="30"><data key="sos-poi-title"><sos:Title>Grid Prototype 1 interface doesn’t allow navigation to groups of POIs other than the current one if they’re not connected</sos:Title></data><data key="sos-poi-text"><sos:Text>The grid interface to navigate/traverse a graph/network doesn’t provide a way to reach from one group of connected POIs to another group of connected POIs if no POIs from the two separate groups share a connection between the groups. The only way to access separate groups is via the fragment identifier if the user knows the ID of a POI of the group, which is very inconvenient and not an interface control.</sos:Text></data></node><node id="1"><data key="sos-poi-title"><sos:Title>The browser is sandboxed</sos:Title></data><data key="sos-poi-text"><sos:Text>Our prototypes are implemented in the browser. The issue is the “Same Origin Policy” and the problem that Cross-Origin Resource Sharing requires the cooperation of remote, external entities in advance.</sos:Text></data></node><node id="2"><data key="sos-poi-title"><sos:Title>Remote code execution</sos:Title></data><data key="sos-poi-text"><sos:Text>The browser executes unchecked code retrieved from remote, external entities. Such code can be malicious. The browser needs to sandbox the execution in order to protect the computer from compromization. Reasons for it are that no software installation is required in advance (dynamic loading and execution on demand), and that the operating systems running the majority of browsers lack the concept of software distribution repositories where code is submitted and checked, as most of the remote code is proprietary, as well as the operating system that supports this model of denying digital freedom to the user, so the code must be obtained from the original author and can’t be fixed (if broken or malicious), to establish and maintain the dependency.</sos:Text></data></node><node id="13"><data key="sos-poi-title"><sos:Title>Manual software installation is inconvenient</sos:Title></data><data key="sos-poi-text"><sos:Text/></data></node><node id="20"><data key="sos-poi-title"><sos:Title>Lock-in dependency on a single online server/domain/storage/service</sos:Title></data><data key="sos-poi-text"><sos:Text/></data></node><node id="3"><data key="sos-poi-title"><sos:Title>Leakage of confidential data</sos:Title></data><data key="sos-poi-text"><sos:Text>If the browser gets and executes unchecked code from various remote, external entities, it could send the confidential data hold by the other code back from where itself came from and leak it.</sos:Text></data></node><node id="4"><data key="sos-poi-title"><sos:Title>Business model of online service dependency</sos:Title></data><data key="sos-poi-text"><sos:Text>Browser vendors tend to be engaged in some form of SaaS online service lock-in dependency business model, so it would harm their business interest if the sandbox wouldn’t enforce the use of these services and instead would allow to make use of local alternatives.</sos:Text></data></node><node id="5"><data key="sos-poi-title"><sos:Title>Limitations for offline use</sos:Title></data><data key="sos-poi-text"><sos:Text>Data can’t be loaded from or stored to the local hard drive. It’s impossible to interoperate with existing other software on the system. It’s impossible to retrieve data from or submit data to a remote server.</sos:Text></data></node><node id="6"><data key="sos-poi-title"><sos:Title>Quasi-reqirement of online use</sos:Title></data><data key="sos-poi-text"><sos:Text>No data exchange can happen conveniently if it isn’t done with the original remote, external server that delivered the web application files. The operator of the server that delivered the web application files will be faced with responsibilities like data protection, preventing data loss, security, quality of service (uptime and providing the service, so if the service is discontinued, people will loose their work), demands of law enforcement, etc. If the user doesn’t have connectivity, some functions won’t work, for example: uploading a file in order to share/publish and then retrieve it again from the original remote server, because local files can’t be added to the local web software.</sos:Text></data></node><node id="7"><data key="sos-poi-title"><sos:Title>No neutral repository</sos:Title></data><data key="sos-poi-text"><sos:Text>The repository for the prototypes and examples is a personal repository that’s attached to skreutzer’s account: https://gitlab.com/skreutzer/sos-experimental</sos:Text></data></node><node id="8"><data key="sos-poi-title"><sos:Title>Bootstrapping</sos:Title></data><data key="sos-poi-text"><sos:Text>No prior discussion, organizational structures or planning, instead: fast prototyping and ad-hoc setup to reduce the costs of potential failure. Adjust dynamically, build for demand, and not find out after a lot of investment that it turns out to be the wrong result. A main concept of Douglas Engelbart, also known from the Agile Movement, also known from the Lean Movement.</sos:Text></data></node><node id="27"><data key="sos-poi-title"><sos:Title>Practical work is difficult and expensive</sos:Title></data><data key="sos-poi-text"><sos:Text>It is very difficult and expensive to influence the manifest design of existing, real systems according to a theoretical plan. Costs can be time, health, timing/opportunity, enjoyment, mental capacity, etc.</sos:Text></data></node><node id="9"><data key="sos-poi-title"><sos:Title>Bad for linking</sos:Title></data><data key="sos-poi-text"><sos:Text>Links to the repository will lead to skreutzer’s account. A redirect likely can’t be set up later, so moving the repository later likely will break existing links.</sos:Text></data></node><node id="10"><data key="sos-poi-title"><sos:Title>Bad context</sos:Title></data><data key="sos-poi-text"><sos:Text>It’s only a single personal repository on skreutzer’s account, where the context and environment holds many other repositories as well that aren’t related to SOS, so somebody who explores the repository wouldn’t find other SOS material, but unrelated projects, which is bad for the discoverability of the SOS projects. Other SOS repositories aren’t collected in one place, but spread and mixed with other stuff, which is confusing. There is no one-stop-shop authoritative place where all the materials can be found.</sos:Text></data></node><node id="32"><data key="sos-poi-title"><sos:Title>Bad for community management</sos:Title></data><data key="sos-poi-text"><sos:Text>It’s difficult and risky for other people to join and participate, if their contributions are bound to a personal account that’s not related to SOS. Connections might get lost for SOS if a transition needs to happen later.</sos:Text></data></node><node id="33"><data key="sos-poi-title"><sos:Title>Bus factor</sos:Title></data><data key="sos-poi-text"><sos:Text>With git, forking is easy and cheap, so it’s not an effect of too much importance yet that the experimental repository for examples and prototypes is operated by a single person and in case of mishap, malicious actions or loss of availability/interest might become inacessible.</sos:Text></data></node><node id="11"><data key="sos-poi-title"><sos:Title>No connections from SOS</sos:Title></data><data key="sos-poi-text"><sos:Text>There’s no connection from the wcharlton user account nor from the official website http://www.untiednations.com/community/plan-sos/ to the repository, which is bad for discoverability and relies solely on wcharlton’s responsibility to indicate the existence of it, in terms of bus factor.</sos:Text></data></node><node id="12"><data key="sos-poi-title"><sos:Title>Unpublished material</sos:Title></data><data key="sos-poi-text"><sos:Text>Some of William Charlton’s material isn’t published like the grid interface mockup drawings, HTML grid interface mockup, ASPX server prototype, the “SOS - Meeting for Untied Nations/The Ecology of Systems Thinking” and “SOS - Meeting for Cape Town Hackathon” files with their corresponding XSLTs.</sos:Text></data></node><node id="14"><data key="sos-poi-title"><sos:Title>No repository</sos:Title></data><data key="sos-poi-text"><sos:Text>In lack of a shared repository or a personal repository, there is no good place to publish them.</sos:Text></data></node><node id="15"><data key="sos-poi-title"><sos:Title>Copyright</sos:Title></data><data key="sos-poi-text"><sos:Text>For the publication of the material to make sense and be useful, it should be licensed properly. This requires William Charlton to consider the licenses and deciding on one or several of them.</sos:Text></data></node><node id="16"><data key="sos-poi-title"><sos:Title>Incompleteness, not open</sos:Title></data><data key="sos-poi-text"><sos:Text>People who look into the project via the site or the sos-experimental repository won’t be able to get an overview of what has been produced so far. Potential collaborators or independent contributors won’t have access to all the files and might start to waste time by producing similar material which was already produced, but isn’t available.</sos:Text></data></node><node id="17"><data key="sos-poi-title"><sos:Title>No versioning</sos:Title></data><data key="sos-poi-text"><sos:Text>It’s difficult to keep track of the different versions of a file and it can’t easily be established from a given file if it is current or an historic version.</sos:Text></data></node><node id="18"><data key="sos-poi-title"><sos:Title>Backup is difficult</sos:Title></data><data key="sos-poi-text"><sos:Text>It takes a lot of effort to spread the individual files in order to have copies of the whole collection everywhere as a backup mechanism if the original repository or (e-mail) accounts become unavailable.</sos:Text></data></node><node id="19"><data key="sos-poi-title"><sos:Title>SOS formats differ</sos:Title></data><data key="sos-poi-text"><sos:Text>Stephan Kreutzer’s example files differ from William Charlton’s example files. Stephan Kreutzer’s prototypes expect a different format than William Charlton’s prototypes expect. Stephan Kreutzer’s example files don’t validate according to the official XSD.</sos:Text></data></node><node id="21"><data key="sos-poi-title"><sos:Title>Not interoperable</sos:Title></data><data key="sos-poi-text"><sos:Text>Because of differing formats, the prototypes are incompatible and example files are specific to only one of the two prototype groups. The examples can’t be demonstrated to work with all of the prototypes.</sos:Text></data></node><node id="23"><data key="sos-poi-title"><sos:Title>SOS is also a human system tool</sos:Title></data><data key="sos-poi-text"><sos:Text>SOS planning is a method/process/procedure, not just a software tool. It’s intended to be used in specific contexts and setups. The prototypes don’t necessarily reflect the methodological context yet.</sos:Text></data></node><node id="24"><data key="sos-poi-title"><sos:Title>Is pre-existing</sos:Title></data><data key="sos-poi-text"><sos:Text>The Meeting is in William Charlton’s example files and prototypes that pre-existed the creation of the prototypes and examples.</sos:Text></data></node><node id="25"><data key="sos-poi-title"><sos:Title>Meetings not reflected in all examples and prototypes</sos:Title></data><data key="sos-poi-text"><sos:Text>Stephan Kreutzer’s examples and prototypes don’t reflect the concept of the Meeting, which leads to incompatibility with William Charlton’s examples and prototypes that do implement the concept of the Meeting.</sos:Text></data></node><node id="26"><data key="sos-poi-title"><sos:Title>Progress isn’t visible</sos:Title></data><data key="sos-poi-text"><sos:Text>Visitors and potential collaborators/contributors can’t find out about the progress of the project.</sos:Text></data></node><node id="28"><data key="sos-poi-title"><sos:Title>Not very engaging</sos:Title></data><data key="sos-poi-text"><sos:Text>Visitors, potential collaborators and potential contributors might not get attracted because of thinking that the project is inactive.</sos:Text></data></node><node id="29"><data key="sos-poi-title"><sos:Title>No production system</sos:Title></data><data key="sos-poi-text"><sos:Text>The examples and prototypes are somewhat fixed/frozen, they serve as mere examples that shouldn’t be polluted with expansion as a result of real-world usage in order to remain useful and concise, with focus on specific features and characteristics. For the real bootstrapping of this project effort, there’s no production system/environment that also allows organizational enhancements like notifications or versioning to track the history.</sos:Text></data></node><node id="31"><data key="sos-poi-title"><sos:Title>Progress is limited/blocked</sos:Title></data><data key="sos-poi-text"><sos:Text>Bootstrapping can’t improve and advance to a higher stage as the existing results aren’t supposed to and don’t contribute to the actual project effort itself.</sos:Text></data></node><edge id="edge-1" source="8" target="30"/><edge id="edge-2" source="2" target="1"/><edge id="edge-3" source="3" target="1"/><edge id="edge-4" source="4" target="1"/><edge id="edge-5" source="13" target="2"/><edge id="edge-6" source="20" target="2"/><edge id="edge-7" source="20" target="4"/><edge id="edge-8" source="1" target="5"/><edge id="edge-9" source="1" target="6"/><edge id="edge-10" source="8" target="7"/><edge id="edge-11" source="27" target="8"/><edge id="edge-12" source="7" target="9"/><edge id="edge-13" source="7" target="10"/><edge id="edge-14" source="7" target="32"/><edge id="edge-15" source="7" target="33"/><edge id="edge-16" source="7" target="11"/><edge id="edge-17" source="8" target="12"/><edge id="edge-18" source="14" target="12"/><edge id="edge-19" source="15" target="12"/><edge id="edge-20" source="12" target="16"/><edge id="edge-21" source="12" target="17"/><edge id="edge-22" source="12" target="18"/><edge id="edge-23" source="8" target="19"/><edge id="edge-24" source="19" target="21"/><edge id="edge-25" source="25" target="21"/><edge id="edge-26" source="23" target="25"/><edge id="edge-27" source="24" target="25"/><edge id="edge-28" source="8" target="26"/><edge id="edge-29" source="26" target="28"/><edge id="edge-30" source="8" target="29"/><edge id="edge-31" source="29" target="31"/><edge id="edge-32" source="30" target="31"/><edge id="edge-33" source="21" target="31"/></graph></graphml>
\ No newline at end of file
......@@ -21,9 +21,9 @@ along with SOS Map Prototype 2. If not, see <http://www.gnu.org/licenses/>.
<xsl:template match="/">
<graphml xmlns="http://graphml.graphdrawing.org/xmlns" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://graphml.graphdrawing.org/xmlns http://graphml.graphdrawing.org/xmlns/1.0/graphml.xsd" xmlns:sos="http://www.untiednations.com/SOS">
<key id="sos-poi-title" for="node" attr.name="label" attr.type="string"/>
<key id="sos-poi-text" for="node" attr.name="description" attr.type="string"/>
<graph id="SOS" edgedefault="directed">
<key id="sos-poi-title" for="node" attr.name="label" attr.type="string"/>
<key id="sos-poi-text" for="node" attr.name="description" attr.type="string"/>
<xsl:apply-templates select="/sos:SOS/sos:POI"/>
<xsl:apply-templates select="/sos:SOS/sos:POI/sos:Parent"/>
</graph>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment