Changes between Version 2 and Version 3 of SandBoxFour
- Timestamp:
- 05/26/09 10:06:54 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SandBoxFour
v2 v3 1 = SandBox no. 4 = 1 SandBox no. 4 2 2 3 3 '''This is just a test. This text is collected from [wiki:ISO15926Primer_Glossary] for testing purposes.''' 4 4 5 5 == Introduction == 6 7 6 There are a great many glossaries available, as well as on-line dictionaries and, of course, Wikipedia. A particularly detailed Glossary is right here: [http://www.btinternet.com/~Chris.Angus/epistle/specifications/glossary/gloss.html STEPDEX: Glossary of Data Management Terms] 8 7 … … 12 11 13 12 == RDF (Resource Description Framework) == 14 15 13 If you dig deeper under the hood of ISO 15926 you will soon run into this term because it is the means of storing the Part 4 definitions. 16 14 … … 18 16 19 17 === Metadata === 20 18 * Metatdata is ''data about data''. For instance, one piece of metadata about the ISO 15926 Primer is that it was written on the POSC/Caesar's wiki website. 21 19 22 20 === Data Model === 23 21 * A data model is an ''abstract'' model that describes how data is represented and accessed. 24 22 25 23 === Abstraction === 26 * ''Abstraction'' is a process of generalizing about something to reduce the information content about an object to only those attributes you are interested in. A typical abstraction is the answer "7600 Glover Road" to the question "Where do you live?" You might live in a beautiful split level house with a wonderful view of the ocean framed by huge 100 year old pine trees but your questioner only wants to know where to have a package delivered.(On the other hand, yours could be a very ordinary house on a very ordinary road, but the city just wants your land for a freeway bypass and the friendly bulldozer operator needs to know where you live.)24 ''Abstraction'' is a process of generalizing about something to reduce the information content about an object to only those attributes you are interested in. A typical abstraction is the answer "7600 Glover Road" to the question "Where do you live?" You might live in a beautiful split level house with a wonderful view of the ocean framed by huge 100 year old pine trees but your questioner only wants to know where to have a package delivered. (On the other hand, yours could be a very ordinary house on a very ordinary road, but the city just wants your land for a freeway bypass and the friendly bulldozer operator needs to know where you live.) ''Abstraction'' is a process of generalizing about something to reduce the information content about an object to only those attributes you are interested in. A typical abstraction is the answer "7600 Glover Road" to the question "Where do you live?" You might live in a beautiful split level house with a wonderful view of the ocean framed by huge 100 year old pine trees but your questioner only wants to know where to have a package delivered. (On the other hand, yours could be a very ordinary house on a very ordinary road, but the city just wants your land for a freeway bypass and the friendly bulldozer operator needs to know where you live.) ''Abstraction'' is a process of generalizing about something to reduce the information content about an object to only those attributes you are interested in. A typical abstraction is the answer "7600 Glover Road" to the question "Where do you live?" You might live in a beautiful split level house with a wonderful view of the ocean framed by huge 100 year old pine trees but your questioner only wants to know where to have a package delivered. (On the other hand, yours could be a very ordinary house on a very ordinary road, but the city just wants your land for a freeway bypass and the friendly bulldozer operator needs to know where you live.) 27 25 28 26 === RDF === 29 27 Putting it all together, then, RDF is: 30 - instructions on how to represent 31 - just the bits of data you are interested in 32 - that describes certain other bits of data 33 - then access it easily 28 29 * instructions on how to represent 30 * just the bits of data you are interested in 31 * that describes certain other bits of data 32 * then access it easily 34 33 35 34 (Whew! I bet you thought that was going to be difficult!) … … 38 37 39 38 === Subject-Predicate-Object Triple Stores === 39 "The ISO 15926 Primer was written on the POSC/Caesar wiki" might be stored in the RDF as the triple: 40 40 41 "The ISO 15926 Primer was written on the POSC/Caesar wiki" might be stored in the RDF as the triple: 42 - the subject: ''ISO 15926 Primer'' 43 - the predicate: ''was written on'' 44 - the object: ''POSC/Caesar wiki'' 41 * the subject: ''ISO 15926 Primer'' 42 * the predicate: ''was written on'' 43 * the object: ''POSC/Caesar wiki'' 45 44 46 45 The each term in the subject-predicate-object may be explicitly named, as in the example above, or they could be in the form of a URI, a ''Uniform Resource Identifier''. 47 46 48 47 === Uniform Resource Identifier === 48 You can think of a ''Uniform Resource Identifier'' as a website for a piece of information. This allows the same resource to be reliably referenced many times. So instead of writing the Subject-Predicate-Object triple as above, it could be rendered as: 49 49 50 You can think of a ''Uniform Resource Identifier'' as a website for a piece of information. This allows the same resource to be reliably referenced many times. So instead of writing the Subject-Predicate-Object triple as above, it could be rendered as: 51 - the subject: 'https://trac.posccaesar.org/wiki/ISO15926Primer' 52 - the predicate: ''was written on'' 53 - the object: ''POSC/Caesar wiki'' 50 * the subject: 'https://trac.posccaesar.org/wiki/ISO15926Primer' 51 * the predicate: ''was written on'' 52 * the object: ''POSC/Caesar wiki'' 54 53 55 54 And in fact we could carry this further by defining somewhere on the Internet the exact meaning of the phrase ''was written on'', and put its URI in the predicate. 56 55 57 56 === More Information about RDF === 58 59 A good place to start if you want to know more about RDF is the ''RDF Primer'' written by the W3C. Be warned, it is not for the feint of heart. But if you can wade through it you will start to see what we mean when we say that "Everything, in the end, is reference data." 57 A good place to start if you want to know more about RDF is the ''RDF Primer'' written by the W3C. Be warned, it is not for the feint of heart. But if you can wade through it you will start to see what we mean when we say that "Everything, in the end, is reference data." 60 58 61 59 http://www.w3.org/TR/REC-rdf-syntax/ 62 60 63 61 ---- 64 65 62 == RDL ( Resource Description Library) == 66 67 63 ... 68 64 69 70 65 ---- 71 72 66 == RDS/WIP (Reference Data System / Working, In Progress) == 73 74 75 67 The RDS/WIP is several things: 76 68 … … 85 77 86 78 ---- 87 88 79 == SPARQL == 89 90 80 Pronounced "sparkle" 91 81 92 93 94 95 96 97 98 99 82 == Conservation of Complexity == 100 101 83 You cannot eliminate complexity. You can move it from one place to another, but it will always be there somewhere. This is used to talk about how we deal with complex Plant information. We can deal with it manually, piece-by-piece, as we have been, or we can ''encapsulate'' it with ISO 15926 and let machines deal with it. 102 84 … … 104 86 105 87 === Encapsulate === 106 107 88 Hiding complexity from users who really don't want to know any more. 108 89 109 110 111 90 ---- 112 113 91 == AEX (Automating Equipment Information Exchange) == 114 92 The Automating Equipment Information Exchange (AEX) project is developing, demonstrating and deploying eXtensible Markup Language (XML) specifications to automate information exchange for the design, procurement, delivery, operation and maintenance of engineered equipment. … … 117 95 118 96 http://www.fiatech.org/projects/idim/aex.htm 119
