IS Week 3/4

In class during late January we began working in XML. XML stands for extensible markup language, and is a text based markup language. XML files consist of tags and attributes. Tags are self descriptive and are used to identify and classify data. This makes XML extensible, one of its key traits. XML is also only capable of storing information, not presenting. XML is also subject to a public standard, as it was published by a public organization. XML is also a type of language known as a markup language. A markup language is one that encodes documents in a format that is both human-readable and machine-readable. This distinguishes it from programming languages in that it cannot run computations or algorithms. XML documents generally begin with a document declaration. These generally contain a version, encoder, and a boolean returning whether the document stands alone. Document declarations are case sensitive. The declaration is then followed by elements. Elements are enclosed within <>, </> brackets. XML documents have a few key elements. First, they have the document declaration. It identifies the document as an XML file and also declares the standalone attributes. These are followed by the XML elements, AKA tags. These are the highest order elements of your file.  

 https://www.w3.org/XML/

Comments

Post a Comment

Popular posts from this blog

IS Week 12

This week we continued our discussion of Information Based Processes and Process Analytics. Specifically, we discussed Process Time Analysis. Process Time Analysis is the calculation of the execution time and cost of a process, using expected cost to account for branching. This must first be done via a time study. Time studies measure how long each activity in a process takes, how long a unit has to wait before processing starts, and then sum the processing and wait time to get flow time. Time studies take branching into account by identifying the likelihood of each branch occurring. Execution time is generally estimated by either observation or random sampling. Alternatively, several experts can be called in to give estimates, followed by a delphi analysis that will weight each of these estimates and provide a master estimate. This is known as single band delphi. Alternatively, wide band delphi can be employed. This is where each expert provides a pessimistic, optimistic, and expected...
Read more

IS Week 11

This week in class we covered information based processes, information flows, and process analytics. There are two prominent ways to model information flows. Every information based process has a couple of inalienable traits: an explicit and measurable goal, specific inputs in the form of information, specific outputs in the form of new information, the use of resources, and having an effect on multiple organizational units. Data is generally modeled via Data Flow Diagrams, whereas activities are generally modeled through Flow Charts. The first thing an analyst must do when modeling a process is identify where the process begins and where it ends. If it is ever unclear how detailed a process should be, an analyst should air on the side of generality, choosing instead to refer to subprocesses that can in turn be modeled on their own. In the modeling of processes, different actors become involved. Popular actors include customers, employees, suppliers, and regulatory agencies. Process mo...
Read more

IS Week 2

This week in IS2000 we largely discussed ontologies. An ontology is the design of formal conceptual structures for a given domain of inquiry. The objective of ontologies, and building them, is to represent abstract, real world physical concepts and their relations in a tangible manner. OOIs represent ontologies within and with regard to information systems. Ontologies describe entities, their attributes, and the relationships between them. Entities are things, physical objects, and abstract concepts. Attributes are properties of entities, as well as measurements of quantitative data with regard to them. Examples of relationship matrices include taxonomies, partonomies and associations. Multiplicities and cardinalities are both examples of constraints. We also sought to answer the question of why we use ontologies. The creation of ontologies forces rigorous analysis and facilitates unambiguous discourse about domains. This is critical for information science, and within the field it i...
Read more